OS/2 2.0 Product Considerations: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
Created page with "02/1992 EEP Terms denoted by a single asterisk (*) in this booklet are trademarks of the IBM Corporation (IBM) in the United States and/or other countries. These terms..."
 
No edit summary
 
(49 intermediate revisions by 2 users not shown)
Line 1: Line 1:
02/1992 EEP
{{Article
|Author=IBM
|Date=1992-02
|OS=OS/2 2.0
|File=N/A
|Source=[https://archive.org/download/minerva2/minerva2.zip/minerva2%2FOS2%2FPRODCONS.ARJ]
}}
Early Experience Program (EEP) - 1992-02
 
==Introduction==
Welcome to the IBM* OS/2* 2.0 02/92 Early Experience Program (EEP). This offering, level 6.304E, is available to those customers who wish to test new functions that have been added to the Limited Availability (LA) product. Not only does this version contain the key functions that were announced for the LA offering at COMDEX/Fall 1991, (including DOS and Windows** compatibility and the OS/2 Workplace Shell, an easy-to-use, icon-based graphical user interface), this version also supports:
* DOS, Windows, and OS/2 applications running in windows, side-by-side, on a single desktop, including Windows applications that run in a PM* window when the primary display adapter is configured for VGA
* A superior platform for customer networking and communications environments, including a graphical login/logout and connection to a LAN, and an ability to browse file server devices (such as printers and disks).
Application developers using pre-release code at level 6.177 may choose to maintain their development environment on 6.177 rather than move to 6.304E. A development environment on 6.304E requires a Developer's Toolkit at level 6.304E.
 
When this product becomes generally available, it is IBM's intent to additionally:
*Provide a superior operating environment through system integrity, performance, interoperability, and ease of use when running DOS, Windows, and OS/2 applications
* Run on Intel 386SX and higher systems.
This booklet describes those product considerations about which you should be aware as you install and use this version of the product. IBM will continue to make enhancements before the product becomes generally available, and we welcome your feedback. This booklet also includes helpful tips and techniques.
 
We recommend that you read this booklet before installing and using the system.
 
This document is a supplement to OS/2 2.0 Getting Started, OS/2 2.0 Using the Operating System, OS/2 2.0 Installation Guide, and OS/2 2.0 Quick Reference. If you are migrating from OS/2 Version 1.3 or Windows Version 3.0, we recommend that you read OS/2 2.0 Migrating to the OS/2 Workplace Shell.
 
==Installation==
*If you are installing this version over an earlier OS/2 2.0 level, select the Format your disk during installation option. This process ensures that any earlier-level files will not be left inadvertently on your hard disk. Be sure to back up any files that you want to save before starting the OS/2 2.0 Installation process.
*If you install this version, you will have to select the Format your disk during installation option when you install the product when it becomes generally available.
*You do not have to format your disk if you are installing over
OS/2 Version 1.2, OS/2 Version 1.3, DOS, or Windows.
*When first prompted to restart (reboot) your system after installation, note that the restart can take about 5 minutes, allowing the OS/2 Workplace Shell to initialize itself.
*If you are installing using a response file, you cannot use the value for Migrate Applications provided in the sample response file. If you wish to migrate existing applications, you must select the Migrate Applications object located in the System Setup folder after OS/2 2.0 has been installed.
* Be sure, if you install a mouse, that it is connected whenever you start your system.
* This product supports two display adapters. If the secondary display adapter is an XGA* or 8514/A adapter, it will run in VGA mode.
* Specific small computer systems interface (SCSI) adapter support for selected SCSI adapter interfaces is included. The device drivers which produce this support are installed in your \OS2 directory, as follows:
 
SCSI Adapter Filename (in \OS2 Directory)
*Adaptec 152x AHA152X.ADD
*Adaptec 154x AHA154X.ADD
*Adaptec 164x AHA164X.ADD
*Future Domain TMC-8xx FD8XX.ADD
*Future Domain TMC-16xx FD16-700.ADD
*Future Domain MCS-600 FD16-700.ADD
*Future Domain MCS-700 FD16-700.ADD
;Note: For the Future Domain TMC-8xx series, the BIOS must be enabled in order for these 8-bit adapters to function.
 
You can manually install this support by adding a BASEDEV=filename statement into CONFIG.SYS. For example, if you have an Adaptec 1542 SCSI adapter in your system, you can install OS/2 support by including the statement BASEDEV=AHA154X.ADD at the end of your CONFIG.SYS file. Make sure you do not include a drive letter or path in this statement.
 
The CONFIG.SYS statement BASEDEV=IBMINT13.I13, included in the CONFIG.SYS file (by default), replaces the DSKBIOS1 function. No special action is required to use any other SCSI hard files. They are supported through the IBMINT13 generic DASD device drivers.
 
==Product Considerations==
IBM will continue testing and enhancing this product before it becomes generally available, and we welcome your feedback.
 
It is our intent to address the limitations described in this Product Considerations section before this product becomes generally available. Where available, we have provided temporary work-arounds.
 
==Performance==
IBM strongly recommends that you do not use this version of the OS/2 2.0 product for performance benchmarking. We will continue to improve performance before the product becomes generally available.
 
IBM's performance objectives for the OS/2 2.0 product are to run DOS and Windows applications equal to or better than they run in their native environments and to run OS/2 applications equal to or better than they run on OS/2 Version 1.3. Based on IBM's measurements of application performance on this version of the product, IBM believes that from a user's perspective, on balance, these performance objectives have been met.
 
Users may experience slower response times when using some system functions, such as loading programs, starting sessions, and switching between sessions. A minimum of 6MB of system memory will improve performance.
 
==OS/2 Workplace Shell==
*The OS/2 2.0 product was designed for use with a mouse. We recommend that you operate the system with a mouse to ensure consistent results.
*In some instances, Help is not available from the Help push button or the F1 key. Refer to the Master Help Index for help on specific topics.
*Copying a folder containing program objects onto a diskette appears successful, but if you try to start or copy the programs from diskette onto another system under this version of the product, the program objects will not be present. (When the OS/2 2.0 product becomes generally available, program objects will not be allowed to be dropped on diskettes).
*The pop-up menu for multiple-selected items does not always display the actions that are common to all the selected objects.
*The size and position of some windows may not be restored after you restart your system.
*Program objects started from command files must have the proper .BAT or .CMD extension specified.
*Copying a read-only folder into another folder creates two folders.
*Displaying an object in Details view does not always display current information about the object. The last access and modification dates may not be current. The column titles may be displayed for file-type objects when none are present in the folder.
*The hard-disk icon in the Drives folder represents tape drives and CD-ROM drives in addition to hard disks.
*The Undo option on the Associations page in the Settings notebooks for a Program object and the Color Palette object are not operational.
*On systems with an XGA adapter connected, you must close each section of the Tutorial before moving to the next section.
*The Special Needs page of the Keyboard object has limited customization capabilities.
*Make sure you select Shut down before you turn off your computer or you might lose data or the position of your icons.
*The Settings notebook for "System" in the System Setup folder has two pages with a "window" tab. The page with the radio buttons for Animation should be used. The other page will be removed.
* If any objects, including folders and programs, are open and running when the system is shut down, only those that were started directly from the desktop will restart when the system is restarted.
To ensure that an object automatically starts when the system is restarted, move the object from its original folder to the desktop. Then, if the object is open when the system is shut down, it will start the next time the system is started.
 
==Desktop Customization==
* If you customize your OS/2 2.0 Desktop to OS/2 1.3 or Windows 3.0, we recommend you read Migrating to the OS/2 Workplace Shell to understand the usability features of your new desktop. The book explains how to make OS/2 2.0 look like OS/2 1.3 or Windows 3.0.
 
==DOS Support==
* When you start a specific version of DOS from a diskette, be sure to insert the diskette in the drive before you start the session.
 
==Windows Support==
* Before cutting and pasting to the OS/2 system clipboard from or to Windows programs, you must start the Clipboard Viewer located in the Productivity folder.
*Bit maps and metafiles greater than 200KB in size will not be transferred successfully to the public clipboard.
*Before running WIN-OS/2* in real mode, reset the DOS setting EMS_ MEMORY_ LIMIT to 0 for the VDM to be used.
*If you choose to copy an existing Windows desktop configuration, it may be necessary to change the MOUSE.DRV statement in SYSTEM.INI. If you are currently using a mouse that creates a statement other than MOUSE.DRV=MOUSE.DRV in the boot.description section of the C:\OS2\MDOS\WINOS2\SYSTEM.INI file (where C: is the startup drive), you will need to change the statement to read MOUSE.DRV=MOUSE.DRV
*Be certain that Windows applications have completed their initialization before switching back to the OS/2 desktop.
 
==OS/2 Printing==
*Ensure that all print job settings notebooks are closed before closing a print object icon or detail view.
 
==Numeric Coprocessor Emulation==
This version of the product will include a numeric coprocessor emulator for use in machines that do not have a numeric coprocessor installed. Currently, we are continuing to improve the accuracy of the results obtained from this emulator. The results obtained from the emulator provided in this version of the product may contain errors and cannot be guaranteed.
   
   
Examples of computations which may lead to erroneous results are those involving high-precision operations, operations combining high-precision operands, boundary conditions such as very large or very small quantities, rounding, and underflow.
   
   
Terms denoted by a single asterisk (*) in this booklet are trademarks of
If you intend to use floating-point operations in mission-critical applications, you must use an 80387 math coprocessor. Installation of an 80387 math coprocessor requires a stepping level of B1 or higher on the 80386 microprocessor.
  the IBM Corporation (IBM) in the United States and/or other countries.
  These terms include:
  Current PM
  IBM Presentation Manager Operating System/2 PS/2
  OS/2 Personal System/2
  XGA WIN-OS/2
  Terms denoted by a double asterisk in this booklet (**) are trademarks of
  other companies. Other trademarks appearing in this booklet are owned
  by their respective companies.
  Microsoft, MS Bookshelf, MS Excel, MS Flight Simulator, MS Money, and Windows are trademarks of Microsoft Corporation.
  IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED,
  INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND
  MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
  DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
  LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.
  Copyright IBM Corporation, 1992, all rights reserved.
1 ******************** Page: iii      ********************
  Contents
  Introduction  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . . . . . .1
  Installation  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . . . . . .3
  Product Considerations  . . . . . . . . . . . .  . . . . . . . . . . . .  .5
  Performance  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . . . . .5
  OS/2 Workplace Shell..........................  5
  Desktop Customization  . . . . . . . . . . . .  . . . . . . . . . . . .  .7
  DOS Support  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . . . . .7
  Windows Support  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . .7
  OS/2 Printing  . . . . . . . . . . . .  . . . . . . . . . . . .  . . . . . . .8
  Numeric Coprocessor Emulation...................  8
  Local Area Network Support......................  9
  Peripheral Devices  . . . . . . . . . . . .  . . . . . . . . . . . .  . . .9
  Personal Computer Manufacturers - Compatibility........  12
  Tips and Techniques.........................  15
  Applications Considerations  . . . . . . . . . . . .  . . . . . . . . . 18
  Summary of Applications.......................  19
  Improvements from the LA Product................  25
  Installation Improvements  . . . . . . . . . . . .  . . . . . . . . . . 25
  Product Considerations Improvements..............  25
  Tips and Techniques Improvements................  28
  Applications Considerations Improvements............  30
  Contents iii
1 ******************** Page: iv      ********************
  iv OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 1        ********************
  Introduction
  Welcome to the IBM* OS/2* 2.0 02/92 Early Experience Program
  (EEP). This offering, level 6.304E, is available to those customers
  who wish to test new functions that have been added to the
  Limited Availability (LA) product. Not only does this version
  contain the key functions that were announced for the LA offering
  at COMDEX/Fall 1991, (including DOS and Windows** compatibility
  and the OS/2 Workplace Shell, an easy-to-use, icon-based
  graphical user interface), this version also supports:
  þ DOS, Windows, and OS/2 applications running in windows,
  side-by-side, on a single desktop, including Windows
  applications that run in a PM* window when the primary
  display adapter is configured for VGA
  þ A superior platform for customer networking and
  communications environments, including a graphical
  login/logout and connection to a LAN, and an ability to browse
  file server devices (such as printers and disks).
  Application developers using pre-release code at level 6.177 may
  choose to maintain their development environment on 6.177 rather
  than move to 6.304E. A development environment on 6.304E
  requires a Developer's Toolkit at level 6.304E.
  When this product becomes generally available, it is IBM's intent
  to additionally:
  þ Provide a superior operating environment through system
  integrity, performance, interoperability, and ease of use when
  running DOS, Windows, and OS/2 applications
  þ Run on Intel 386SX and higher systems.
  This booklet describes those product considerations about which
  you should be aware as you install and use this version of the
  product. IBM will continue to make enhancements before the
  product becomes generally available, and we welcome your
  feedback. This booklet also includes helpful tips and techniques.
  Introduction1
1 ******************** Page: 2        ********************
  We recommend that you read this booklet before installing and
  using the system.
  This document is a supplement to OS/2 2.0 Getting Started,  OS/2
  2.0 Using the Operating System,  OS/2 2.0 Installation Guide , and
  OS/2 2.0 Quick Reference. If you are migrating from OS/2 Version
  1.3 or Windows Version 3.0, we recommend that you read  OS/2 2.0
  Migrating to the OS/2 Workplace Shell.
  2 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 3        ********************
  Installation
  þ If you are installing this version over an earlier OS/2 2.0 level,
  select the  Format your disk during installation  option. This
  process ensures that any earlier-level files will not be left
  inadvertently on your hard disk. Be sure to back up any files
  that you want to save before starting the OS/2 2.0 Installation
  process.
  þ If you install this version, you will have to select the  Format
  your disk during installation  option when you install the
  product when it becomes generally available.
  þ You do not  have to format your disk if you are installing over
  OS/2 Version 1.2, OS/2 Version 1.3, DOS, or Windows.
  þ When first prompted to restart (reboot) your system after
  installation, note that the restart can take about 5 minutes,
  allowing the OS/2 Workplace Shell to initialize itself.
  þ If you are installing using a response file, you cannot use the
  value for  Migrate Applications  provided in the sample response
  file. If you wish to migrate existing applications, you must
  select the Migrate Applications object located in the System
  Setup folder after OS/2 2.0 has been installed.
  þ Be sure, if you install a mouse, that it is connected whenever
  you start your system.
  þ This product supports two display adapters. If the secondary
  display adapter is an XGA* or 8514/A adapter, it will run in
  VGA mode.
  þ Specific small computer systems interface (SCSI) adapter
  support for selected SCSI adapter interfaces is included. The
  device drivers which produce this support are installed in your
  \OS2 directory, as follows:
  SCSI Adapter Filename (in \OS2 Directory)
  Adaptec 152x AHA152X.ADD
  Adaptec 154x AHA154X.ADD
  Adaptec 164x AHA164X.ADD
  Installation3
1 ******************** Page: 4        ********************
  Future Domain TMC-8xx FD8XX.ADD
  Future Domain TMC-16xx FD16-700.ADD
  Future Domain MCS-600 FD16-700.ADD
  Future Domain MCS-700 FD16-700.ADD
  Note:  For the Future Domain TMC-8xx series, the BIOS must
  be enabled in order for these 8-bit adapters to function.
  You can manually install this support by adding a
  BASEDEV=filename statement into CONFIG.SYS. For
  example, if you have an Adaptec 1542 SCSI adapter in your
  system, you can install OS/2 support by including the
  statement BASEDEV=AHA154X.ADD at the end of your
  CONFIG.SYS file. Make sure you do not  include a drive letter
  or path in this statement.
  The CONFIG.SYS statement BASEDEV=IBMINT13.I13, included
  in the CONFIG.SYS file (by default), replaces the DSKBIOS1
  function. No special action is required to use any other SCSI
  hard files. They are supported through the IBMINT13 generic
  DASD device drivers.
  4 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 5        ********************
  Product Considerations
  IBM will continue testing and enhancing this product before it
  becomes generally available, and we welcome your feedback.
  It is our intent to address the limitations described in this Product
  Considerations  section before this product becomes generally
  available. Where available, we have provided temporary
  work-arounds.
  Performance
  IBM strongly recommends that you do not use this version of the
  OS/2 2.0 product for performance benchmarking. We will continue
  to improve performance before the product becomes generally
  available.
  IBM's performance objectives for the OS/2 2.0 product are to run
  DOS and Windows applications equal to or better than they run in
  their native environments and to run OS/2 applications equal to or
  better than they run on OS/2 Version 1.3. Based on IBM's
  measurements of application performance on this version of the
  product, IBM believes that from a user's perspective, on balance,
  these performance objectives have been met.
  Users may experience slower response times when using some
  system functions, such as loading programs, starting sessions, and
  switching between sessions. A minimum of 6MB of system
  memory will improve performance.
  OS/2 Workplace Shell
  þ The OS/2 2.0 product was designed for use with a mouse. We
  recommend that you operate the system with a mouse to
  ensure consistent results.
  þ In some instances, Help is not available from the  Help  push
  button or the F1 key. Refer to the Master Help Index for help
  on specific topics.
  Product Considerations5
1 ******************** Page: 6        ********************
  þ Copying a folder containing program objects onto a diskette
  appears successful, but if you try to start or copy the programs
  from diskette onto another system under this version of the
  product, the program objects will not be present. (When the
  OS/2 2.0 product becomes generally available, program
  objects will not be allowed to be dropped on diskettes).
  þ The pop-up menu for multiple-selected items does not always
  display the actions that are common to all the selected objects.
  þ The size and position of some windows may not be restored
  after you restart your system.
  þ Program objects started from command files must have the
  proper .BAT or .CMD extension specified.
  þ Copying a read-only folder into another folder creates two
  folders.
  þ Displaying an object in Details view does not always display
  current information about the object. The last access and
  modification dates may not be current. The column titles may
  be displayed for file-type objects when none are present in the
  folder.
  þ The hard-disk icon in the Drives folder represents tape drives
  and CD-ROM drives in addition to hard disks.
  þ The Undo option on the Associations page in the Settings
  notebooks for a Program object and the Color Palette object
  are not operational.
  þ On systems with an XGA adapter connected, you must close
  each section of the Tutorial before moving to the next section.
  þ The Special Needs page of the Keyboard object has limited
  customization capabilities.
  þ Make sure you select Shut down  before you turn off your
  computer or you might lose data or the position of your icons.
  þ The Settings notebook for ]SystemØ in the System Setup folder
  has two pages with a ]windowØ tab. The page with the radio
  buttons for Animation should be used. The other page will be
  removed.
  6 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 7        ********************
  þ If any objects, including folders and programs, are open and
  running when the system is shut down, only those that were
  started directly from the desktop will restart when the system
  is restarted.
  To ensure that an object automatically starts when the system
  is restarted, move the object from its original folder to the
  desktop. Then, if the object is open when the system is shut
  down, it will start the next time the system is started.
  Desktop Customization
  þ If you customize your OS/2 2.0 Desktop to OS/2 1.3 or Windows
  3.0, we recommend you read Migrating to the OS/2 Workplace
  Shell  to understand the usability features of your new desktop.
  The book explains how to make OS/2 2.0 look like OS/2 1.3 or
  Windows 3.0.
  DOS Support
  þ When you start a specific version of DOS from a diskette, be
  sure to insert the diskette in the drive before you start the
  session.
  Windows Support
  þ Before cutting and pasting to the OS/2 system clipboard from
  or to Windows programs, you must start the Clipboard Viewer
  located in the Productivity folder.
  þ  Bit maps and metafiles greater than 200KB in size will not be
  transferred successfully to the public clipboard.
  þ Before running WIN-OS/2* in real mode, reset the DOS setting
  EMS_ MEMORY_ LIMIT to 0 for the VDM to be used.
  þ If you choose to copy an existing Windows desktop
  configuration, it may be necessary to change the MOUSE.DRV
  statement in SYSTEM.INI. If you are currently using a mouse
  that creates a statement other than MOUSE.DRV=MOUSE.DRV
  in the boot.description section of the
  C:\OS2\MDOS\WINOS2\SYSTEM.INI file (where C: is the startup
  Product Considerations7
1 ******************** Page: 8        ********************
  drive), you will need to change the statement to read
  MOUSE.DRV=MOUSE.DRV
  þ  Be certain that Windows applications have completed their
  initialization before switching back to the OS/2 desktop.
  OS/2 Printing
  þ Ensure that all print job settings notebooks are closed before
  closing a print object icon or detail view.
  Numeric Coprocessor Emulation
  This version of the product will include a numeric coprocessor
  emulator for use in machines that do not have a numeric
  coprocessor installed. Currently, we are continuing to improve the
  accuracy of the results obtained from this emulator. The results
  obtained from the emulator provided in this version of the product
  may contain errors and cannot be guaranteed.
  Examples of computations which may lead to erroneous results
  are those involving high-precision operations, operations
  combining high-precision operands, boundary conditions such as
  very large or very small quantities, rounding, and underflow.
  If you intend to use floating-point operations in mission-critical
  applications, you must use an 80387 math coprocessor. Installation
  of an 80387 math coprocessor requires a stepping level of B1 or
  higher on the 80386 microprocessor.
  If you are in doubt about whether your application uses
  floating-point operations, contact the application vendor.
  8 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 9        ********************
  Local Area Network Support
  þ Opening a network group folder in a tree may be slow if your
  network contains many servers. It is recommended that you
  use icon view instead.
  þ The network folder cannot be moved from the desktop.
  þ The *Alias  server folder displayed by LAN Server 2.0 is not
  functional.
  þ If you are a LAN Server Network Administrator, do not change
  the printer configuration on a server once it has been shared.
  þ If you log in as a LAN Server Network Administrator and some
  functions are not available, display the pop-up menu and
  select Refresh. The administrator functions are now available.
  þ Occasionally, the pop-up menu of a network object might show
  login  when you are already logged in, or logout  when you are
  already logged out. Click on login/logout  and redisplay the
  pop-up menu.
  þ In this version, do not attempt to access DOS LAN requesters
  from WIN-OS/2 when you are running a specific version of DOS
  in a DOS session.
  Refer to Product Supplemental Information for LAN Server Version
  2.0  for current information regarding network support.
  Peripheral Devices
  þ When using your Logitech mouse when running in standalone
  DOS, you may experience problems with your mouse under
  OS/2. If so, unplug and then plug in your mouse, or, after
  shutdown, power down and then power up your system.
  þ When using the COM port on a PS/2* Model 90 or 95 with
  Enhanced set to ON, be sure that the Serial Transmit and
  Serial Receive Arbitration Levels in the hardware configuration
  are set to Dedicated , with different numbers specified.
  For example, when the Serial Port is set to SERIAL 2 in the
  hardware configuration, its corresponding Serial Transmit
  Product Considerations9
1 ******************** Page: 10      ********************
  Arbitration Level should be set to DEDICATED 3. The Serial
  Receive  Arbitration Level must be set to DEDICATED 4.
  When both levels of a serial port are set to Shared , data
  communication and printing from the COM port with Enhanced
  set to ON will not operate properly. Run the  Setup/Diagnostics
  diskette and follow the instructions on the screen to change
  your hardware configuration.
  þ The OS/2 2.0 product has been designed to allow most DOS
  and Windows applications to run more reliably than in their
  native environments.
  One or more DOS applications typically can be run
  concurrently in windows while in the background, although
  there are some performance trade-offs when DOS graphics
  applications are run in a window. To realize the full benefits of
  the OS/2 2.0 product, run these applications in full-screen
  sessions.
  There are three cases in which DOS graphics applications may
  be suspended (receive no processor time) when running in the
  background:
  ¯ In the first case, a DOS multiplane application that uses
  advanced graphics, such as 640x480x16 or 640x350x16, will
  be suspended, regardless of the graphics adapter installed,
  if any other DOS application is running in the foreground in
  a full-screen session.
  ¯ In the second case, a multiplane DOS application that uses
  advanced graphics, such as 640x480x16 or 640x350x16, will
  be suspended when a Presentation Manager session is
  running in the foreground in XGA mode. Currently, this
  situation occurs even if you have an Extended Graphics
  Array (XGA) and a Video Graphics Array (VGA) adapter
  connected to your system.
  ¯ In the third case, a multiplane DOS application that uses
  1024x768x16 graphics mode will be suspended when a
  Presentation Manager session is running in the foreground
  in 8514/A mode.
  Note that suspending DOS applications running in the
  background generally poses no problem unless the
  10 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 11      ********************
  applications are timing-dependent, such as communications or
  process-control applications. In these cases, suspending them
  may cause them to fail. Avoid this situation by running these
  applications in the foreground in full-screen sessions only. If
  they are graphics applications, run them only in a single-plane
  mode, such as 640x200x2, 320x200x256, or 640x480x2, in
  full-screen sessions.
  Note also that for WIN-OS/2 sessions, set the
  VIDEO_ SWITCH_ NOTIFICATION DOS setting to ON to avoid
  having Windows programs suspended when running in the
  background.
  Product Considerations 11
1 ******************** Page: 12      ********************
  Personal Computer Manufacturers - Compatibility
  The following list depicts those Personal Computer Manufacturers'
  systems that have passed IBM's compatibility test with the current
  OS/2 2.0 EEP product. IBM's compatibility test verifies (18) key
  functions of the OS/2 2.0 operating system. These test results are
  based on selected model configurations provided by the PCM to
  IBM. This list is preliminary, and IBM will continually update the
  list as we proceed with our testing. Current information will be
  disseminated on various electronic forums and bulletin boards.
  þ ACER 1125Eþ COMPAQ 486/50L
  þ ALR BusinessSTATIONþ COMPUADD 320SC Model
  486SX/20 Model 101 A002
  þ ALR BusinessSTATIONþ COMPUADD 325 Model
  386DX Model 1 A000
  þ ALR BusinessVEISA 486/33þ COMPUADD 333T Model
  Model 101 A005
  þ ALR BusinessVEISA 386/33þ COMPUADD 433E Model
  Model 1 A005
  þ ALR MPS Modular 386/33þ CUMULUS GLC 486DX/33
  þ ALR MPS Modular 486/33þ CUMULUS 486SX/20
  þ ALR POWERPRO 33/486þ CUMULUS GLC 386SX/20
  Model SMP 128/150þ CUMULUS GLC 386DX/25
  þ ALR PowerFlex 20Xþ CUMULUS GLC 386DX/33
  þ ALR PowerFlex Flyerþ DELL PowerLine 433DE
  þ AMAX PC/486-33þ DELL System 320SX
  þ APRICOT LS 386SX-20 w/cache
  þ APRICOT Qi 486-25þ DELL System 333D
  þ AST Premium II 486SX/20þ DELL System 486D/25
  þ AST Premium II 386/33þ DELL System 325P
  þ AT&T SAFARI NSX/20þ DELL System 320N+
  þ COMPAQ DESKPRO 386/25Eþ DYNEX 386-25
  þ COMPAQ DESKPROþ EVEREX 486/33E
  386/25M EX0-2904D-01EL
  þ COMPAQ DESKPRO 386/Sþ EVEREX 486/33
  þ COMPAQ SYSTEMPRO EX0-2904D-B1
  Model 3002þ EVEREX 386/33
  þ COMPAQ SYSTEMPRO EX0-2804-000L
  Model 3000þ GRID GRIDCASE 1550sx
  12 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 13      ********************
  þ GRID MFP/420sþ OLIVETTI P750 Model
  þ GRID 386sx/MFP20 XP2670
  þ HERTZ 486/33þ REPLY D32-386-330 Model
  þ HEWLETT PACKARD Vectra 32MCA
  386/25þ REPLY D32-486-250 Model
  þ HEWLETT PACKARD Vectra 32MCA
  RS/25Cþ REPLY 486-33
  þ HEWLETT PACKARD Vectraþ SAMSUNG DeskMaster
  486/33T 386S/25
  þ INTEL LP386SX/20þ SIEMENS NIXDORF
  þ MEMOREX-TELEX Model PCD-3Msx/20
  8267þ SIEMENS NIXDORF
  þ MEMOREX-TELEX Model PCD-3Bsx
  8290þ TATUNG TCS8640S
  þ NCR SYSTEM 3300/3421þ TATUNG TCS8800D
  Model 2014þ TATUNG TCS9600T
  þ NCR SYSTEM 3300/3432þ TOSHIBA T3100SX
  Model 1000þ TOSHIBA T5200/100
  þ NCR SYSTEM 3300/3433þ ZENITH Data Systems
  Model 2000 Z-486SX/25E
  þ NCR SYSTEM 3400 Modelþ ZENITH Data Systems
  3000 Z-486/33E
  þ OLIVETTI M300-10 Modelþ ZEOS 386DX-33CT
  XP2655þ ZEOS 386SX-208DT
  þ ZEOS 486DX-33T
  Note:  The compatibility test information provided herein is
  provided for information purposes. IBM MAKES NO
  WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO
  THE OPERATION OF THE PERSONAL COMPUTERS LISTED.
  þ In order for microchannel systems with ESDI hard disks to
  operate properly:
  1. On OS/2 Diskette 1, rename ABIOS.SYS to ABIOS.HLD.
  2. Createa null file called ABIOS.SYS. For example:
  Personal Computer Manufacturers - Compatibility 13
1 ******************** Page: 14      ********************
   
   
If you are in doubt about whether your application uses floating-point operations, contact the application vendor.
==Local Area Network Support==
* Opening a network group folder in a tree may be slow if your network contains many servers. It is recommended that you use icon view instead.
* The network folder cannot be moved from the desktop.
* The *Alias server folder displayed by LAN Server 2.0 is not functional.
* If you are a LAN Server Network Administrator, do not change the printer configuration on a server once it has been shared.
* If you log in as a LAN Server Network Administrator and some functions are not available, display the pop-up menu and select Refresh. The administrator functions are now available.
* Occasionally, the pop-up menu of a network object might show login when you are already logged in, or logout when you are already logged out. Click on login/logout and redisplay the pop-up menu.
* In this version, do not attempt to access DOS LAN requesters from WIN-OS/2 when you are running a specific version of DOS in a DOS session.
Refer to Product Supplemental Information for LAN Server Version 2.0 for current information regarding network support.
==Peripheral Devices==
* When using your Logitech mouse when running in standalone DOS, you may experience problems with your mouse under OS/2. If so, unplug and then plug in your mouse, or, after shutdown, power down and then power up your system.
* When using the COM port on a PS/2* Model 90 or 95 with Enhanced set to ON, be sure that the Serial Transmit and Serial Receive Arbitration Levels in the hardware configuration are set to Dedicated, with different numbers specified.
For example, when the Serial Port is set to SERIAL 2 in the hardware configuration, its corresponding Serial Transmit Arbitration Level should be set to DEDICATED 3. The Serial Receive Arbitration Level must be set to DEDICATED 4. When both levels of a serial port are set to Shared, data communication and printing from the COM port with Enhanced set to ON will not operate properly. Run the Setup/Diagnostics diskette and follow the instructions on the screen to change your hardware configuration.
* The OS/2 2.0 product has been designed to allow most DOS and Windows applications to run more reliably than in their native environments.
One or more DOS applications typically can be run concurrently in windows while in the background, although there are some performance trade-offs when DOS graphics applications are run in a window. To realize the full benefits of the OS/2 2.0 product, run these applications in full-screen sessions.
   
   
There are three cases in which DOS graphics applications may be suspended (receive no processor time) when running in the background:
:*In the first case, a DOS multiplane application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended, regardless of the graphics adapter installed, if any other DOS application is running in the foreground in a full-screen session.
:*In the second case, a multiplane DOS application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended when a Presentation Manager session is running in the foreground in XGA mode. Currently, this situation occurs even if you have an Extended Graphics Array (XGA) and a Video Graphics Array (VGA) adapter connected to your system.
:*In the third case, a multiplane DOS application that uses 1024x768x16 graphics mode will be suspended when a Presentation Manager session is running in the foreground in 8514/A mode.
Note that suspending DOS applications running in the background generally poses no problem unless the applications are timing-dependent, such as communications or process-control applications. In these cases, suspending them may cause them to fail. Avoid this situation by running these applications in the foreground in full-screen sessions only. If they are graphics applications, run them only in a single-plane mode, such as 640x200x2, 320x200x256, or 640x480x2, in full-screen sessions.
Note also that for WIN-OS/2 sessions, set the VIDEO_ SWITCH_ NOTIFICATION DOS setting to ON to avoid having Windows programs suspended when running in the background.
==Personal Computer Manufacturers - Compatibility==
The following list depicts those Personal Computer Manufacturers' systems that have passed IBM's compatibility test with the current OS/2 2.0 EEP product. IBM's compatibility test verifies (18) key functions of the OS/2 2.0 operating system. These test results are based on selected model configurations provided by the PCM to IBM. This list is preliminary, and IBM will continually update the list as we proceed with our testing. Current information will be disseminated on various electronic forums and bulletin boards.
{|
|
*ACER 1125E
*ALR BusinessSTATION
*ALR BusinessSTATION
*ALR BusinessVEISA 486/33
*ALR BusinessVEISA 386/33
*ALR MPS Modular 386/33
*ALR MPS Modular 486/33
*ALR POWERPRO 33/486
*ALR PowerFlex 20X
*ALR PowerFlex Flyer
*AMAX PC/486-33
*APRICOT LS 386SX-20 w/cache
*APRICOT Qi 486-25
*AST Premium II 486SX/20
*AST Premium II 386/33
*AT&T SAFARI NSX/20
*COMPAQ DESKPRO 386/25E
*COMPAQ DESKPRO 386/S
*COMPAQ SYSTEMPRO EX0-2904D-B1 Model 3002
*COMPAQ DESKPRO
*COMPAQ SYSTEMPRO EX0-2804-000L Model 3000
*COMPAQ 486/50L
*COMPUADD 320SC Model 486SX/20 Model 101 A002
*COMPUADD 325 Model 386DX Model 1 A000
*COMPUADD 333T Model Model 101 A005
*COMPUADD 433E Model Model 1 A005
|
*CUMULUS GLC 486DX/33
*CUMULUS 486SX/20
*CUMULUS GLC 386SX/20 Model SMP 128/150
*CUMULUS GLC 386DX/25
*CUMULUS GLC 386DX/33
*DELL PowerLine 433DE
*DELL System 320SX
*DELL System 333D
*DELL System 486D/25
*DELL System 325P
*DELL System 320N+
*DYNEX 386-25
*EVEREX 486/33E 386/25M EX0-2904D-01EL
*EVEREX 486/33
*EVEREX 386/33
*GRID GRIDCASE 1550sx
*GRID MFP/420s
*GRID 386sx/MFP20 XP2670
*HERTZ 486/33
*HEWLETT PACKARD Vectra 32MCA 386/25
*HEWLETT PACKARD Vectra 32MCA RS/25C
*HEWLETT PACKARD Vectra 486/33T
*INTEL LP386SX/20
*MEMOREX-TELEX Model 8267
*MEMOREX-TELEX Model 8290
|
*NCR SYSTEM 3300/3421 Model 2014
*NCR SYSTEM 3300/3432
*NCR SYSTEM 3300/3433
*NCR SYSTEM 3400 Model
*OLIVETTI M300-10 Model
*OLIVETTI P750 Model
*REPLY D32-486-250 Model
*REPLY D32-386-330 Model
*REPLY 486-33
*SAMSUNG DeskMaster 386S/25
*SIEMENS NIXDORF PCD-3Msx/20
*SIEMENS NIXDORF PCD-3Bsx
*TATUNG TCS8640S
*TATUNG TCS8800D
*TATUNG TCS9600T
*TOSHIBA T3100SX Model 1000
*TOSHIBA T5200/100
*ZENITH Data Systems Model 2000 Z-486SX/25E
*ZENITH Data Systems 3000 Z-486/33E
*ZEOS 386DX-33CT XP2655
*ZEOS 386SX-208DT
*ZEOS 486DX-33T
|}
Note: The compatibility test information provided herein is provided for information purposes. IBM MAKES NO
WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE OPERATION OF THE PERSONAL COMPUTERS LISTED.
*In order for microchannel systems with ESDI hard disks to operate properly:
1. On OS/2 Diskette 1, rename ABIOS.SYS to ABIOS.HLD.
2. Create a null file called ABIOS.SYS. For example:
   COPY CON: ABIOS.SYS
   COPY CON: ABIOS.SYS
   blank space
   blank space
Line 1,055: Line 224:
   PF6
   PF6
   Enter
   Enter
  3. Begin your installation.
3. Begin your installation.
* An ABIOS timing condition between OS/2 2.0 and the ALR MPS systems can occur during operation. To ensure this condition is not encountered, IBM and ALR have agreed to a temporary solution. The following change should be made to the CONFIG.SYS file on Installation Diskette 1 and after installation, ensuring that the same change appears in the CONFIG.SYS file on the hard disk.
  þ An ABIOS timing condition between OS/2 2.0 and the ALR MPS
 
  systems can occur during operation. To ensure this condition
Change BASEDEV=IBM1FPLY.ADD to BASEDEV=IBM1FLPY.ADD /PS2
  is not encountered, IBM and ALR have agreed to a temporary
 
  solution. The following change should be made to the
and
  CONFIG.SYS file on Installation Diskette 1 and after installation,
 
  ensuring that the same change appears in the CONFIG.SYS file
Change BASEDEV=IBM2FLPY.ADD to rem BASEDEV=IBM2FLPY.ADD After Installation Diskette 4:
  on the hard disk.
# Put the Installation Diskette in drive A.
# Reboot.
  Change BASEDEV=IBM1FPLY.ADD
# Continue until Diskette1 introduction.
  to BASEDEV=IBM1FLPY.ADD /PS2
# Escape (Esc) from Diskette1 to the A: prompt.
# Make the same change to C:\CONFIG.SYS.
  and
# Copy IBM1FLPY.ADD to C:\OS2 directory.
# Remove the diskette.
  Change BASEDEV=IBM2FLPY.ADD
# Reboot and continue the installation.
  to rem BASEDEV=IBM2FLPY.ADD
 
  After Installation Diskette 4:
==Tips and Techniques==
* You can improve the performance of some applications by adjusting the DOS settings. If the application does not use extended or expanded memory, these values can be set to zero:
  1. Put the Installation Diskette in drive A.
:*IDLE_ SENSITIVITY
:*EMS_ MEMORY_ LIMIT
  2. Reboot.
:*XMS_ MEMORY_ LIMIT.
  3. Continue until Diskette1 introduction.
For more information on DOS settings, refer to the OS/2 2.0 online Master Help Index.
*If you want to use the asynchronous communications device interface (ACDI) support in the OS/2 2.0 mini-application called PM Terminal, you must edit your CONFIG.SYS file and then restart your system. For IBM PS/2 computers, install the SASYNCDB.SYS driver:
  4. Escape (Esc) from Diskette1 to the A: prompt.
DEVICE=C:\OS2\APPS\SASYNCDB.SYS
  5. Make the same change to C:\CONFIG.SYS.
For 80386 compatibles, install the SASYNCDA.SYS driver:
  6. Copy IBM1FLPY.ADD to C:\OS2 directory.
  7. Remove the diskette.
  8. Reboot and continue the installation.
  14 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 15      ********************
  Tips and Techniques
  þ You can improve the performance of some applications by
  adjusting the DOS settings. If the application does not use
  extended or expanded memory, these values can be set to
  zero:
  ¯ IDLE_ SENSITIVITY
  ¯ EMS_ MEMORY_ LIMIT
  ¯ XMS_ MEMORY_ LIMIT.
  For more information on DOS settings, refer to the OS/2 2.0
  online Master Help Index.
  þ If you want to use the asynchronous communications device
  interface (ACDI) support in the OS/2 2.0 mini-application called
  PM Terminal, you must edit your CONFIG.SYS file and then
  restart your system. For IBM PS/2 computers, install the
  SASYNCDB.SYS driver:
  DEVICE=C:\OS2\APPS\SASYNCDB.SYS
  For 80386 compatibles, install the SASYNCDA.SYS driver:
   DEVICE=C:\OS2\APPS\SASYNCDA.SYS
   DEVICE=C:\OS2\APPS\SASYNCDA.SYS
When files are transferred to or from a drive other than drive C in PM Terminal, the dialog box may not display all the subdirectories. To correct this problem, select the C drive and then reselect the correct alternative drive.
* Using the OS/2 Enhanced Editor:
:*The maximum line length is 237 characters.
:*When naming your files, you are unable to use blanks and some nonalphanumeric characters, such as double quotes, apostrophes, and brackets.
*The FIND option in the OS/2 System Editor does not display the results of a search. To view these results, press Alt+F6 to move the focus from the Find dialog box to the text entry area.
*We have improved the high-performance file system (HPFS) by adding new options that users can specify. Also, we have improved both the HPFS and the File Allocation Table (FAT) file systems by expanding the read-ahead logic for small-record input/output (I/O) of less than 512 bytes in size. These enhancements are expected to provide faster performance when sequential reads are performed.
   
   
  When files are transferred to or from a drive other than drive C
Use the IFS= statement to define the maximum I/O record size that can be cached using the HPFS.
  in PM Terminal, the dialog box may not display all the
* By default, 2MB is the amount of memory allocated to each WIN-OS/2 session. Currently, we recommend 2MB for each WIN-OS/2 session you plan to run.
  subdirectories. To correct this problem, select the C drive and
  then reselect the correct alternative drive.
  þ Using the OS/2 Enhanced Editor:
  ¯ The maximum line length is 237 characters.
  ¯ When naming your files, you are unable to use blanks and
  some nonalphanumeric characters, such as double quotes,
  apostrophes, and brackets.
  þ The FIND option in the OS/2 System Editor does not display the
  results of a search. To view these results, press Alt+F6 to
  move the focus from the Find dialog box to the text entry area.
  þ We have improved the high-performance file system (HPFS) by
  adding new options that users can specify. Also, we have
  improved both the HPFS and the File Allocation Table (FAT) file
  systems by expanding the read-ahead logic for small-record
  Tips and Techniques 15
   
   
If you receive an error indicating that your WIN-OS/2 session has insufficient memory, you can try adjusting the memory to 3MB or 4MB. However, this setting should not be set high arbitrarily because the OS/2 swap file (SWAPPER.DAT) will be allowed to grow in proportion to the amount of additional memory you allocate.
   
   
The optimum size of the swap file is relative to your environment. If the swap file is located in its own partition, it is preferable to be conservative when you specify the size of that partition. These specifications may be helpful.  
1 ******************** Page: 16      ********************
  input/output (I/O) of less than 512 bytes in size. These
  enhancements are expected to provide faster performance
  when sequential reads are performed.
  Use the IFS= statement to define the maximum I/O record
  size that can be cached using the HPFS.
  þ By default, 2MB is the amount of memory allocated to each
  WIN-OS/2 session. Currently, we recommend 2MB for each
  WIN-OS/2 session you plan to run.
  If you receive an error indicating that your WIN-OS/2 session
  has insufficient memory, you can try adjusting the memory to
  3MB or 4MB. However, this setting should not be set high
  arbitrarily because the OS/2 swap file (SWAPPER.DAT) will be
  allowed to grow in proportion to the amount of additional
  memory you allocate.
  The optimum size of the swap file is relative to your
  environment. If the swap file is located in its own partition, it
  is preferable to be conservative when you specify the size of
  that partition. These specifications may be helpful.
   4MB system : 7 to 12MB
   4MB system : 7 to 12MB
   6MB system : 5 to 10MB
   6MB system : 5 to 10MB
   8MB system : 3 to 8MB
   8MB system : 3 to 8MB
  þ OS/2 allows you to run a specific version of DOS in a DOS
*OS/2 allows you to run a specific version of DOS in a DOS session along with the OS/2 2.0 product. This feature helps to ensure compatibility with applications, such as block device drivers, that otherwise would be incompatible with the OS/2 2.0 environment. Currently,  
  session along with the OS/2 2.0 product. This feature helps to
:*If you have already started a version of DOS from a diskette, you will not be able to start another version of DOS from your hard disk.
  ensure compatibility with applications, such as block device
:*You may experience problems when starting, or booting, DOS from your A drive or from other drives.
  drivers, that otherwise would be incompatible with the OS/2 2.0
:*You cannot start multiple copies of a specific version of DOS using a single image. To make multiple images, create them on your hard disk using the VMDISK.EXE utility located in the \OS2\MDOS\ directory. Change the DOS_ STARTUP_ DRIVE DOS setting to start from the image you created.  
  environment. Currently,
*When asked to specify a directory from which to add fonts, do not specify the C:\OS2\DLL path, where C: is your startup drive.
 
  ¯ If you have already started a version of DOS from a
==Applications Considerations==
  diskette, you will not be able to start another version of
===Temporary Limitations===
  DOS from your hard disk.
IBM has tested many DOS, Windows and OS/2 applications. Most of them run unchanged, but some require special attention when running on this version of the product. IBM currently plans to address these limitations before the OS/2 2.0 product becomes generally available. Where available, we have suggested temporary work-arounds.
  ¯ You may experience problems when starting, or booting,
  DOS from your A drive or from other drives.
  ¯ You cannot start multiple copies of a specific version of
  DOS using a single image. To make multiple images,
  create them on your hard disk using the VMDISK.EXE utility
  located in the \OS2\MDOS\ directory. Change the
  DOS_ STARTUP_ DRIVE DOS setting to start from the image
  you created.
  16 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 17      ********************
  þ When asked to specify a directory from which to add fonts, do
  not specify the C:\OS2\DLL path, where C: is your startup
  drive.
  Tips and Techniques 17
1 ******************** Page: 18      ********************
  Applications Considerations
  Temporary Limitations
  IBM has tested many DOS, Windows and OS/2 applications. Most
  of them run unchanged, but some require special attention when
  running on this version of the product. IBM currently plans to
  address these limitations before the OS/2 2.0 product becomes
  generally available. Where available, we have suggested
  temporary work-arounds.
  Other Limitations
  Some categories of applications, usually because of their design or
  because they use undocumented interfaces, will not operate
  properly with the OS/2 2.0 product. IBM is in the process of
  contacting these vendors about resolving these incompatibilities.
  Some vendors have already developed a fix and are willing to
  make the fix available. These have been noted.
  These five categories of applications include:
  þ Applications that use the DOS Protect-Mode Interface, the
  Expanded Memory Specification (EMS), or the Extended
  Memory Specification (XMS) are supported. Other DOS
  extenders, such as the virtual control-program interface (VCPI),
  that require exclusive access to the 80386 control registers,
  are not supported because they could violate the integrity of
  the system.
  þ Functions in applications that directly address the physical
  sectors to perform write operations are not supported because
  these operations could violate the integrity of the system.
  þ Some Windows applications invoke the Windows
  mini-applications to run a subset of function. If you did not
  format your hard disk when you installed this version of the
  product, and if you already had Windows Version 3.0 installed,
  these mini-applications will be invoked automatically.
  þ Windows applications that require enhanced mode
  þ DOS or Windows applications that use undocumented DOS or
  Windows interfaces
  18 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 19      ********************
  Summary of Applications
  Application Result Comment
  Ansel DOS program - The See ]Temporary
  program is not LimitationsØ on page 18.
  operational.
  AutoCAD OS/2 program - The Close the program only
  program does not return from the desktop.
  to a command prompt upon exit. See ]Other LimitationsØ on
  page 18.
  Auto Manager DOS program - The Install the real mode
  program cannot be version. The program
  installed if you try to expects COMMAND.COM
  use the version that uses extended memory. to be in the root directory of C:\. Copy
  COMMAND.COM to the C:\
  directory from the
  C:\OS2\MDOS
  \COMMAND.COM
  directory.
  See ]Other LimitationsØ on
  page 18.
  Borland C++ 2.0 DOS program - The Use the standard version.
  Turbo C++ extended versions of See ]Other LimitationsØ on
  Turbo Pascal these programs use non-DPMI DOS page 18.
  extenders.
  Central Point Backup DOS program - The program will provide its Run in a DOS full-screen session.
  own graphic fonts when
  running in a DOS See ]Other LimitationsØ on
  session. page 18.
  Peachtree Complete III DOS program - The Set the DOS setting,
  5.0 program requires more DOS_ FILES to 40.
  than 40 file handles to See ]Temporary
  run and non standard LimitationsØ on page 18.
  ASCII characters may be displayed.
  Codeview for Windows Windows program - The See ]Temporary
  Version 3.0 program debugger is unable to load a LimitationsØ on page 18.
  program for debugging.
  Applications Considerations 19
1 ******************** Page: 20      ********************
  Application Result Comment
  Distinct Backup Windows program - The Back up to a hard disk.
  message See ]Temporary
  ]Unrecoverable floppy LimitationsØ on page 18.
  disk errorØ may be displayed when you try
  to back up to diskette.
  Fastback Plus 2.1 DOS program - The Back up to a hard disk.
  program is unable to
  support backing up to a See]Other LimitationsØ on
  diskette. page 18 .
  FastLynx DOS program - The Remove the DEVICE=
  program is unable to C:\OS2\MDOS\VCOM.SYS
  establish a connection statement from the
  when VCOM.SYS is CONFIG.SYS file.
  installed. If parallel port is used, no problems are
  encountered.
  FormBase 1.2 Windows program - The AUTOEXEC.BAT file is Use an editor to remove the SHARE command from
  automatically updated the AUTOEXEC.BAT file.
  with the SHARE
  statement.
  Freelance/G OS/2 program - You will Lotus will provide a fix to
  not be able to install install on the OS/2 2.0
  some options because product or install under
  the program looks for an OS/2 Version 1.3.
  earlier version of OS/2 (for example, OS/2 See ]Other LimitationsØ on
  version 1.x). page 18.
  LapLink III 3.0 DOS program - Your serial ports may not Remove the VCOM.SYS and COM.SYS statements
  operate properly. from your CONFIG.SYS
  file.
  See ]Other LimitationsØ on
  page 18.
  Magellan DOS program - The Use the OS/2 UNDELETE
  UNDELETE functions in command.
  the program require See ]Other LimitationsØ on
  physical sector page 18.
  addressing.
  MagiCorp Windows program - Run this program by itself
  Running this program or try restarting the
  along with other WIN-OS/2 session.
  programs in Windows sessions may cause the See ]Temporary
  system to stop. LimitationsØ on page 18.
  20 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 21      ********************
  Application Result Comment
  Mathcad Windows program - The Install under DOS.
  program cannot be See ]Temporary
  installed under OS/2. LimitationsØ on page 18.
  More Windows Windows program - Use only the other three
  Full-page white mode modes.
  splits the screen, and See ]Temporary
  the screen receives a LimitationsØ on page 18.
  mirror image and then
  repaints the desktop.
  MS Bookshelf - DOS Multimedia See ]Other LimitationsØ on
  CD-ROM Reference program - The program page 18.
  Library requires the device driver MOUSE.COM
  Version 6.14 to run.
  MS Excel OS/2 program - The help Avoid using these
  index and the keyboard functions.
  help do not operate
  properly. See ]Temporary LimitationsØ on page 18.
  MS Money 1.0 Windows program - The program invokes the Use the Calculator mini-application in the
  Windows Version 3.0 OS/2 Productivity folder.
  mini-application called
  Calculator for See ]Other LimitationsØ on page 18.
  computations.
  Multimedia Extensions DOS program - This Include the
  installation program program starts its own UseOS2shield=0
  for Windows desktop program and statement in your
  assumes that if it is not the first application SYSTEM.INI file before starting the multimedia
  loaded, another desktop extensions program. Then
  is running. reedit the SYSTEM.INI file
  to say UseOS2shield=1
  after you have installed
  the Windows multimedia
  extensions and before starting other WIN-OS/2
  sessions.
  See]Other LimitationsØ on
  page 18 .
  MusicPrinter Plus DOS program - The program cannot be Install the program under DOS and run it under
  started in a DOS OS/2.
  session. See]Other LimitationsØ on
  page 18 .
  Applications Considerations 21
1 ******************** Page: 22      ********************
  Application Result Comment
  Norton Backup 1.2 DOS program - Backing See ]Temporary
  up to diskette may be LimitationsØ on page 18.
  very slow.
  Norton Desktop Windows program - The Include the
  program assumes that if UseOS2shield=1
  it is not  the first application loaded, statement in your SYSTEM.INI file in the
  another desktop is \OS2\MDOS\WINOS2
  running. directory on your start-up
  drive.
  See ]Other LimitationsØ on
  page 18.
  Norton Utilities 5.0 DOS program - The Use the OS/2 UNDELETE
  UNDELETE functions in command.
  the program require See ]Other LimitationsØ on
  physical sector page 18.
  addressing.
  Omnipage Windows program - The See ]Other LimitationsØ on
  Professional 1.0 program must run in 386 page 18.
  enhanced mode.
  Oracle DOS program - The See ]Other LimitationsØ on
  program cannot be page 18.
  installed.
  Paradox 3.5 DOS program - The Use the standard version
  extended version of the of the program
  program (PARADOXK.EXE) uses (PARADOXR.EXE).
  non-DPMI extenders. See ]Other LimitationsØ on
  page 18.
  Persuasion 2.0 Windows program - Use LPT1 to print.
  Printing from COM1 may Deselect the public option
  produce unexpected results. on the clipboard.
  See ]Temporary
  If the clipboard is set to LimitationsØ on page 18.
  public, the program is unable to copy to the
  clipboard.
  ProComm 2.0 DOS program - The Avoid using the SHELL
  ProComm SHELL command.
  command starts the
  OS/2 shell instead of the See ]Temporary LimitationsØ on page 18.
  DOS shell, and the DOS
  session stops.
  22 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 23      ********************
  Application Result Comment
  Publishers PowerPak Windows program - The Create the following
  2.1 program does not create directory:
  the C:\POWERPAK C:\OS2\MDOS
  directory because the directory appears to \WINOS2\POWERPAK; then run the installation batch
  exist. file.
  See ]Temporary
  LimitationsØ on page 18.
  Quicken for Windows Windows program - The program invokes the Use the Calculator mini-application in the
  Windows Version 3.0 OS/2 Productivity folder.
  mini-appication called See ]Other LimitationsØ on
  Calculator for page 18.
  computations.
  SideKick OS/2 program - The Install a printer and be
  Notepad does not sure that it is present on
  operate properly. the desktop. Avoid
  minimizing the Notepad.
  See ]Temporary
  LimitationsØ on page 18.
  Smartfax DOS program - The See]Other LimitationsØ on
  program does not page 18
  operate properly.
  TAPCIS DOS program - The Run FIX_ FIND.COM before
  TAPCIS.HLP file cannot running TAPCIS. This is a
  be found. Terminate and Stay Resident program in the
  OS2\MDOS directory.
  See ]Temporary
  LimitationsØ on page 18.
  Wing Commander II DOS program - The program is not Select the No Sound  option during the Wing
  operational or runs very Commander II installation
  slowly in a DOS session. to improve performance.
  See ]Temporary
  LimitationsØ on page 18.
  Applications Considerations 23
1 ******************** Page: 24      ********************
  Application Result Comment
  Wordperfect for Windows program - The Find the file
  Windows program may not WPWINFIL.EXE in the
  operate properly. Wordperfect directory and
  run:
  FIXWPÚ path¿  WPWINFIL.EXE
  For additional information
  contact Wordperfect at
  1-800-228-6076 or 1-800-228-1029.
  See ]Temporary
  LimitationsØ on page 18.
  24 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 25      ********************
  Improvements from the LA Product
  Some of the restrictions identified in the LA Product
  Considerations  document have been corrected in this EEP version
  of the product. These items include:
  Installation Improvements
  þ A response file can be used to install OS/2 2.0. See the OS/2
  2.0 Installation Guide  for details.
  þ The DSKBIOS1 function discussed in the LA document is now
  included in the BASEDEV=IBMINT13.I13 CONFIG.SYS
  statement, by default. No special actions are required to
  operate SCSI devices.
  þ If you select not to install some Productivity and Games
  programs, blank icons representing these programs will no
  longer be installed.
  þ DOS LAN requesters no longer require that DOS have control
  of the system. They will run on a booted version in a VDM.
  þ The time needed to install the OS/2 has been reduced.
  Product Considerations Improvements
  OS/2 Workplace Shell
  þ You can delete multiple objects individually, or you can delete
  them all at one time.
  þ An icon representing Drive A will appear on the desktop.
  Double-clicking on this icon will now provide access to Drive A.
  þ The settings notebooks for the Drives objects are now
  operational when displayed from the object's pop-up menu.
  þ Actions performed on fonts no longer produce inconsistent
  results.
  þ The time needed to shut down the system has been reduced.
  Improvements from the LA Product 25
1 ******************** Page: 26      ********************
  Windows Support
  þ The following items are now described in the OS/2 2.0 online
  or hard copy documentation:
  ¯ Follow the manufacturer's instructions to install Windows
  applications under the OS/2 2.0 product. If the installation
  is unsuccessful, start a full-screen DOS session and try
  again. Another alternative is to choose  Run  from the File
  menu of the WIN-OS/2 Program Manager.
  ¯ To start Windows applications, do one of the following:
  - Install them as separate objects on your desktop.
  - Select Run  from the WIN-OS/2 Program Manager.
  - Type WINOS2  followed by the program name in a
  full-screen DOS or OS/2 session.
  Note that you cannot run DOS applications using Run  from
  the File menu of the Program Manager. They must be run
  from the (OS/2) desktop.
  ¯ OS/2's Dynamic Data Exchange (DDE) feature allows you to
  dynamically update and change data in one running
  program and effect those changes in another running
  program.
  Note that before performing DDE between an OS/2 and a
  Windows application, you must start the Data Update
  object in the Productivity folder.
  ¯ Not all clipboard and DDE data formats are transferable to
  the public clipboard or shared between Windows and PM
  applications.
  ¯ You must run Windows applications in a single WIN-OS/2
  session if you are using private Windows data formats.
  ¯ A set of WIN-OS/2 printer drivers is included with this
  product. When you create an OS/2 printer, you will be
  asked if you want a Windows-equivalent configuration, if
  one is available. You also will be asked to install a
  WIN-OS/2 printer driver.
  If a WIN-OS/2 printer is not automatically installed during
  OS/2 installation, you can install WIN-OS/2 printer drivers
  26 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 27      ********************
  from the WIN-OS/2 Control Panel. WIN-OS/2 printer drivers
  are located on the Printer Driver Diskettes 1-6.
  If you want to use a Windows printer driver that is not
  automatically installed by OS/2, or is not shipped with
  OS/2, configure the Windows printer driver to use an OS/2
  port that has the IBMNULL printer driver associated with it.
  The IBMNULL printer driver is installed during system
  installation. If IBMNULL is not displayed in the list of
  available printer drivers, use the Install  pop-up menu
  choice on an existing printer driver to display the Printer
  Driver Install dialog box.
  1. Insert Printer Driver Diskette1 in your diskette drive;
  then select Refresh.
  2. Select IBMNULL from the list; then select Install.
  3. Select Cancel; then select IBMNULL for the Printer
  object.
  Note that LPT1.OS2 and LPT2.OS2 support better
  performance than LPT1 or LPT2 when configuring from the
  WIN-OS/2 Control Panel.
  þ Performing DDE between two Windows applications running in
  separate sessions or between a Presentation Manager (PM)
  and a Windows application currently no longer cause the
  Windows application running in the background to be
  suspended (receive no processor time).
  þ If the Windows clipboard is set to public, requests to print the
  screen from a Windows session (using PrintScreen) are now
  successful.
  þ The contents of the clipboard are no longer lost if you exit from
  a Windows application during a cut, copy, or paste operation.
  þ Bit-map files and metafiles can be converted compatibly
  between Windows and PM applications when operating in all
  video modes.
  þ To install your Windows LAN device drivers and configure
  WIN-OS/2 to use these device drivers, run SETUP.EXE from the
  WIN-OS/2 full screen session.
  þ It is not necessary to define a Windows printer if you are
  installing Windows multimedia extensions under this version.
  Improvements from the LA Product 27
1 ******************** Page: 28      ********************
  þ Like Windows, the OS/2 2.0 product automatically installs
  corresponding Windows mouse and printer drivers when you
  select a Presentation Manager*  mouse driver.
  þ On systems with an XGA adapter connected, starting Windows
  from a full-screen session and then closing the session no
  longer causes the screen to behave inconsistently.
  OS/2 Printing
  þ You can now delete any printer device drivers from the Printer
  object. Doing so no longer causes subsequent attempts to
  reinstall these drivers to fail.
  Peripheral Devices
  þ The DOS DISKCOPY command now operates properly when
  used on an external 5 1/4-inch diskette drive.
  Tips and Techniques Improvements
  þ The OS/2 mini-application called Cat and Mouse is now
  operational.
  þ Closing a DOS or Windows session from the Window List or
  from a pop-up menu, while an application is running in that
  session, no longer causes subsequent attempts (by these
  sessions) to access devices to fail.
  þ HPFS performance for 2KB and 4KB I/O has been improved.
  þ All networking applications may now start from the Drives
  objects.
  28 OS/2 2.0 02/92 EEP Product Considerations
1 ******************** Page: 29      ********************
  þ The following items are now described in the OS/2 2.0 online
  documentation:
  ¯ Adjusting these DOS settings for Windows full-screen
  objects or other Windows program objects, may boost the
  performance of applications running in Windows sessions.
  KBD_CTRL_BYPASS = CTRL_ESC This setting allows the WIN-OS/2
  Program Manager to recognize
  a Ctrl+Esc and then
  display the Task List.
  MOUSE_EXCLUSIVE_ACCESS = ON This setting allows WIN-OS/2
  (in place of the PM)
  to control the Mouse pointer
  if you run a WIN-OS/2
  session in a window.
  VIDEO_SWITCH_NOTIFICATION = ON This setting notifies a DOS
  program to do its own save
  and restore of the video state.
  VIDEO_8514A_XGA_IOTRAP = OFF This setting must be set so
  that DOS and WIN-OS/2 sessions
  can continue to run when in the
  background (for systems with
  8514/A and XGA adapters only).
  ¯ The performance of DOS applications is optimal when
  running in full- screen sessions. You can press the
  Alt+Home keys to run your DOS applications in full-screen
  DOS sessions.
  ¯ If you are running Windows and have an 8514 Windows
  video adapter (8514.DRV) installed, do not change the
  default settings for VIDEO_ SWITCH_ NOTIFICATION and
  VIDEO_ 8514_ XGA_ IOTRAP.
  Improvements from the LA Product 29
1 ******************** Page: 30      ********************
  Applications Considerations Improvements
  The following applications, restricted in the LA version of this
  product, are now supported:
  þ Borland C++ 3.0
  þ Chipchat
  þ Control Room 1.0
  þ Crosstalk IV
  þ Dynacomm
  þ Framework III Version 1.1
  þ IBM Current*
  þ MS Flight Simulator
  þ MS Word for OS/2
  þ New Wave 3.0
  þ PC3270
  þ PC Paintbrush IV
  þ PFS First Choice 3.1
  þ Superprint 2.0
  þ Terminator
  þ Winfax Pro 2.0
   
   
===Other Limitations===
Some categories of applications, usually because of their design or because they use undocumented interfaces, will not operate properly with the OS/2 2.0 product. IBM is in the process of contacting these vendors about resolving these incompatibilities.
Some vendors have already developed a fix and are willing to make the fix available. These have been noted.
   
   
These five categories of applications include:
*Applications that use the DOS Protect-Mode Interface, the Expanded Memory Specification (EMS), or the Extended Memory Specification (XMS) are supported. Other DOS extenders, such as the virtual control-program interface (VCPI), that require exclusive access to the 80386 control registers, are not supported because they could violate the integrity of the system.
*Functions in applications that directly address the physical sectors to perform write operations are not supported because these operations could violate the integrity of the system.
*Some Windows applications invoke the Windows mini-applications to run a subset of function. If you did not format your hard disk when you installed this version of the product, and if you already had Windows Version 3.0 installed, these mini-applications will be invoked automatically.
*Windows applications that require enhanced mode
*DOS or Windows applications that use undocumented DOS or Windows interfaces
==Summary of Applications==
{|class="wikitable"
!Application||Result||Comment
|-
|Ansel||DOS program - The program is not operational.||See ''Temporary Limitations'' on page 18.
|-
|AutoCAD||OS/2 program - The program does not return from the desktop.||Close the program only to a command prompt upon exit. See ''Other Limitations'' on page 18.
|-
|Auto Manager||DOS program - The program cannot be installed if you try to use the version that uses extended memory.||Install the real mode version. The program expects COMMAND.COM to be in the root directory of C:\. Copy COMMAND.COM to the C:\ directory from the C:\OS2\MDOS\COMMAND.COM directory.
See Other Limitations on page 18.
|-
|Borland C++ 2.0||DOS program - The Turbo C++ extended versions of Turbo Pascal these programs use non-DPMI DOS extenders.||Use the standard version.
See [Other Limitations] on page 18.
|-
|Central Point Backup||DOS program - The program will provide its own graphic fonts when running in a DOS session.||Run in a DOS full-screen session. See [Other Limitations] on page 18.
|-
|Peachtree Complete III||DOS program - The||Set the DOS setting, DOS_FILES to 40.
5.0 program requires more than 40 file handles to Temporary
run and non standard ASCII characters may be displayed.
See [Limitations] on page 18.
|-
|Codeview for Windows Version 3.0||Windows program - The||See ]Temporary
program debugger is unable to load a LimitationsØ on page 18.
program for debugging.
|-
|Distinct Backup||Windows program - The Back up to a hard disk.
message See ]Temporary
]Unrecoverable floppy LimitationsØ on page 18.
disk errorØ may be displayed when you try
to back up to diskette.
|-
|Fastback Plus 2.1||DOS program - The program is unable to support backing up to a diskette.||Back up to a hard disk.
See [Other Limitations] on page 18.
|-
|FastLynx||DOS program - The program is unable to establish a connection when VCOM.SYS is installed.||Remove the DEVICE=C:\OS2\MDOS\VCOM.SYS statement from the CONFIG.SYS file. If parallel port is used, no problems are encountered.
|-
|FormBase 1.2||Windows program - The AUTOEXEC.BAT file is automatically updated with the SHARE statement.||Use an editor to remove the SHARE command from the AUTOEXEC.BAT file.
|-
|Freelance/G||OS/2 program - You will not be able to install some options because the program looks for an earlier version of OS/2 (for example, OS/2 version 1.x).||Lotus will provide a fix to install on the OS/2 2.0 product or install under OS/2 Version 1.3.
See [Other Limitations] on page 18.
|-
|LapLink III 3.0||DOS program - Your serial ports may not operate properly.||Remove the VCOM.SYS and COM.SYS statements from your CONFIG.SYS file.
See [Other Limitations] on page 18.
|-
|Magellan||DOS program - The UNDELETE functions in the program require physical sector addressing.||Use the OS/2 UNDELETE command.
See [Other Limitations] on page 18.
|-
|MagiCorp||Windows program - Running this program along with other WIN-OS/2 programs in Windows sessions may cause the system to stop.||Run this program by itself or try restarting the session.
   
   
See [Temporary Limitations] on page 18.
|-
|Mathcad||Windows program - The program cannot be installed under OS/2.||Install under DOS.
See [Temporary Limitations] on page 18.
|-
|More Windows||Windows program - Full-page splits the screen, and the screen receives a mirror image and then repaints the desktop.||Use only the other three white mode modes.
See [Temporary Limitations] on page 18.
|-
|MS Bookshelf||DOS Multimedia CD-ROM Reference program - The program Library requires the device driver MOUSE.COM Version 6.14 to run.
|See [Other Limitations] on page 18.
|-
|MS Excel||OS/2 program - The help index and the help do not operate properly.||Avoid using these keyboard functions.
See [Temporary Limitations] on page 18.
|-
|MS Money 1.0||Windows program - The program invokes the mini-application called Calculator for computations.||Use the Calculator mini-application in the Windows Version 3.0 OS/2 Productivity folder.
See [Other Limitations] on page 18.
|-
|Multimedia Extensions||DOS program - This Include the installation program program starts its own UseOS2shield=0 for Windows desktop program and statement in your assumes that if it is not the first application SYSTEM.INI file before starting the multimedia loaded, another desktop extensions program. Then is running. reedit the SYSTEM.INI file to say UseOS2shield=1
after you have installed the Windows multimedia extensions and before starting other WIN-OS/2 sessions.
See [Other Limitations] on page 18.
|-
|MusicPrinter Plus||DOS program - The program cannot be started in a DOS session.||Install the program under DOS and run it under OS/2.
See [Other Limitations] on page 18.
|-
|Norton Backup 1.2||DOS program - Backing up to diskette may be very slow.||See [Temporary Limitations] on page 18.
|-
|Norton Desktop||Windows program - The program assumes that if it is not the first application loaded, another desktop is running.||Include the UseOS2shield=1 statement in your SYSTEM.INI file in the \OS2\MDOS\WINOS2 directory on your start-up drive.
See [Other Limitations] on page 18.
|-
|Norton Utilities 5.0||DOS program - The UNDELETE functions in the program require physical sector addressing.||Use the OS/2 UNDELETE command.
See [Other Limitations] on page 18.
|-
|Omnipage Professional 1.0||Windows program - The program must run in 386 enhanced mode.||See ]Other LimitationsØ on page 18.
|-
|Oracle||DOS program - The program cannot be installed.||See ]Other LimitationsØ on page 18.
|-
|Paradox 3.5||DOS program - The extended version of the program (PARADOXK.EXE) uses non-DPMI extenders.||Use the standard version of the program (PARADOXR.EXE).
See [Other Limitations] on page 18.
|-
|Persuasion 2.0||Windows program - Printing from COM1 may produce unexpected results. If the clipboard is set to public, the program is unable to copy to the clipboard.||Use LPT1 to print. Deselect the public option on the clipboard.
See [Temporary Limitations} on page 18.
|-
|ProComm 2.0||DOS program - The ProComm SHELL command starts the OS/2 shell instead of the DOS shell, and the DOS session stops.||Avoid using the SHELL command.
See [Temporary Limitations] on page 18.
|-
|Publishers PowerPak||Windows program - The 2.1 program does not create the C:\POWERPAK directory because the directory appears to exist.||Create the following directory: C:\OS2\MDOS\WINOS2\POWERPAK; then run the installation batch file.
See [Temporary Limitations] on page 18.
|-
|Quicken for Windows||Windows program - The program invokes the mini-appication called computations.||Use the Calculator mini-application in the Windows Version 3.0 OS/2 Productivity folder.
See [Other Limitations] on Calculator for page 18.
|-
|SideKick||OS/2 program - The Notepad does not operate properly.||Install a printer and be sure that it is present on the desktop. Avoid minimizing the Notepad.
See [Temporary Limitations] on page 18.
|-
|Smartfax||DOS program - The program does not operate properly.||See [Other Limitations] on page 18
|-
|TAPCIS||DOS program - The TAPCIS.HLP file cannot be found.||Run FIX_FIND.COM before running TAPCIS. This is a Terminate and Stay Resident program in the OS2\MDOS directory.
See [Temporary Limitations] on page 18.
|-
|Wing Commander II||DOS program - The program is not operational or runs very slowly in a DOS session.||Select the No Sound option during the Wing Commander II installation to improve performance.
See [Temporary Limitations] on page 18.
|-
|Wordperfect for Windows||Windows program - The program may not operate properly.||Find the file WPWINFIL.EXE in the Wordperfect directory and run:
FIXWP \path\WPWINFIL.EXE
For additional information contact Wordperfect at 1-800-228-6076 or 1-800-228-1029.
   
   
See [Temporary Limitations] on page 18.
|}
==Improvements from the LA Product==
Some of the restrictions identified in the LA Product Considerations document have been corrected in this EEP version of the product. These items include:
===Installation Improvements===
*A response file can be used to install OS/2 2.0. See the OS/2 2.0 Installation Guide for details.
*The DSKBIOS1 function discussed in the LA document is now included in the BASEDEV=IBMINT13.I13 CONFIG.SYS statement, by default. No special actions are required to operate SCSI devices.
*If you select not to install some Productivity and Games programs, blank icons representing these programs will no longer be installed.
*DOS LAN requesters no longer require that DOS have control of the system. They will run on a booted version in a VDM.
* The time needed to install the OS/2 has been reduced.
===Product Considerations Improvements===
====OS/2 Workplace Shell====
*You can delete multiple objects individually, or you can delete them all at one time.
*An icon representing Drive A will appear on the desktop.
:Double-clicking on this icon will now provide access to Drive A.
*The settings notebooks for the Drives objects are now operational when displayed from the object's pop-up menu.
*Actions performed on fonts no longer produce inconsistent results.
*The time needed to shut down the system has been reduced.
====Windows Support====
*The following items are now described in the OS/2 2.0 online or hard copy documentation:
:*Follow the manufacturer's instructions to install Windows applications under the OS/2 2.0 product. If the installation is unsuccessful, start a full-screen DOS session and try again. Another alternative is to choose Run from the File menu of the WIN-OS/2 Program Manager.
:*To start Windows applications, do one of the following:
:*Install them as separate objects on your desktop.
:*Select Run from the WIN-OS/2 Program Manager.
:*Type WINOS2 followed by the program name in a full-screen DOS or OS/2 session.
::Note that you cannot run DOS applications using Run from the File menu of the Program Manager. They must be run from the (OS/2) desktop.
:*OS/2's Dynamic Data Exchange (DDE) feature allows you to dynamically update and change data in one running program and effect those changes in another running program.
Note that before performing DDE between an OS/2 and a Windows application, you must start the Data Update object in the Productivity folder.
:*Not all clipboard and DDE data formats are transferable to the public clipboard or shared between Windows and PM applications.
:*You must run Windows applications in a single WIN-OS/2 session if you are using private Windows data formats.
   
   
:*A set of WIN-OS/2 printer drivers is included with this product. When you create an OS/2 printer, you will be asked if you want a Windows-equivalent configuration, if one is available. You also will be asked to install a WIN-OS/2 printer driver.
   
   
If a WIN-OS/2 printer is not automatically installed during OS/2 installation, you can install WIN-OS/2 printer drivers from the WIN-OS/2 Control Panel. WIN-OS/2 printer drivers are located on the Printer Driver Diskettes 1-6.
If you want to use a Windows printer driver that is not automatically installed by OS/2, or is not shipped with OS/2, configure the Windows printer driver to use an OS/2 port that has the IBMNULL printer driver associated with it.
The IBMNULL printer driver is installed during system installation. If IBMNULL is not displayed in the list of available printer drivers, use the Install pop-up menu choice on an existing printer driver to display the Printer Driver Install dialog box.
1. Insert Printer Driver Diskette1 in your diskette drive; then select Refresh.
2. Select IBMNULL from the list; then select Install.
3. Select Cancel; then select IBMNULL for the Printer object.
Note that LPT1.OS2 and LPT2.OS2 support better performance than LPT1 or LPT2 when configuring from the WIN-OS/2 Control Panel.
* Performing DDE between two Windows applications running in separate sessions or between a Presentation Manager (PM) and a Windows application currently no longer cause the Windows application running in the background to be suspended (receive no processor time).
* If the Windows clipboard is set to public, requests to print the screen from a Windows session (using PrintScreen) are now successful.
* The contents of the clipboard are no longer lost if you exit from a Windows application during a cut, copy, or paste operation.
* Bit-map files and metafiles can be converted compatibly between Windows and PM applications when operating in all video modes.
*To install your Windows LAN device drivers and configure WIN-OS/2 to use these device drivers, run SETUP.EXE from the WIN-OS/2 full screen session.
*It is not necessary to define a Windows printer if you are installing Windows multimedia extensions under this version.
*Like Windows, the OS/2 2.0 product automatically installs corresponding Windows mouse and printer drivers when you select a Presentation Manager* mouse driver.
*On systems with an XGA adapter connected, starting Windows from a full-screen session and then closing the session no longer causes the screen to behave inconsistently.
   
   
====OS/2 Printing====
* You can now delete any printer device drivers from the Printer object. Doing so no longer causes subsequent attempts to reinstall these drivers to fail.
====Peripheral Devices====
* The DOS DISKCOPY command now operates properly when used on an external 5 1/4-inch diskette drive.
==Tips and Techniques Improvements==
*The OS/2 mini-application called Cat and Mouse is now operational.
* Closing a DOS or Windows session from the Window List or from a pop-up menu, while an application is running in that session, no longer causes subsequent attempts (by these sessions) to access devices to fail.
*HPFS performance for 2KB and 4KB I/O has been improved.
*All networking applications may now start from the Drives objects.
*The following items are now described in the OS/2 2.0 online documentation:
:*Adjusting these DOS settings for Windows full-screen objects or other Windows program objects, may boost the performance of applications running in Windows sessions.
:;KBD_CTRL_BYPASS = CTRL_ESC
::This setting allows the WIN-OS/2 Program Manager to recognize a Ctrl+Esc and then display the Task List.
:;MOUSE_EXCLUSIVE_ACCESS = ON
::This setting allows WIN-OS/2 (in place of the PM) to control the Mouse pointer if you run a WIN-OS/2 session in a window.
:;VIDEO_SWITCH_NOTIFICATION = ON
::This setting notifies a DOS program to do its own save and restore of the video state.
:;VIDEO_8514A_XGA_IOTRAP = OFF
::This setting must be set so that DOS and WIN-OS/2 sessions can continue to run when in the background (for systems with 8514/A and XGA adapters only).
:*The performance of DOS applications is optimal when running in full-screen sessions. You can press the Alt+Home keys to run your DOS applications in full-screen DOS sessions.
:*If you are running Windows and have an 8514 Windows video adapter (8514.DRV) installed, do not change the default settings for VIDEO_SWITCH_NOTIFICATION and VIDEO_8514_XGA_IOTRAP.
==Applications Considerations Improvements==
The following applications, restricted in the LA version of this product, are now supported:
* Borland C++ 3.0
* Chipchat
* Control Room 1.0
* Crosstalk IV
* Dynacomm
* Framework III Version 1.1
* IBM Current*
* MS Flight Simulator
* MS Word for OS/2
* New Wave 3.0
* PC3270
* PC Paintbrush IV
* PFS First Choice 3.1
* Superprint 2.0
* Terminator
* Winfax Pro 2.0
==Disclaimers==
Terms denoted by a single asterisk (*) in this booklet are trademarks of the IBM Corporation (IBM) in the United States and/or other countries.
These terms include:
*Current PM
*IBM Presentation Manager Operating System/2 PS/2
*OS/2 Personal System/2
*XGA WIN-OS/2
   
   
Terms denoted by a double asterisk in this booklet (**) are trademarks of
other companies. Other trademarks appearing in this booklet are owned
by their respective companies.
   
   
*Microsoft, MS Bookshelf, MS Excel, MS Flight Simulator, MS Money, and Windows are trademarks of Microsoft Corporation.
   
   
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.
   
   
  30 OS/2 2.0 02/92 EEP Product Considerations
Copyright IBM Corporation, 1992, all rights reserved.
 
[[Category:IBM Publication‎]]

Latest revision as of 18:35, 2 March 2025

Article Info
Author IBM
Date 1992-02
OS Version OS/2 2.0
Companion File N/A
Source [1]

Early Experience Program (EEP) - 1992-02

Introduction

Welcome to the IBM* OS/2* 2.0 02/92 Early Experience Program (EEP). This offering, level 6.304E, is available to those customers who wish to test new functions that have been added to the Limited Availability (LA) product. Not only does this version contain the key functions that were announced for the LA offering at COMDEX/Fall 1991, (including DOS and Windows** compatibility and the OS/2 Workplace Shell, an easy-to-use, icon-based graphical user interface), this version also supports:

  • DOS, Windows, and OS/2 applications running in windows, side-by-side, on a single desktop, including Windows applications that run in a PM* window when the primary display adapter is configured for VGA
  • A superior platform for customer networking and communications environments, including a graphical login/logout and connection to a LAN, and an ability to browse file server devices (such as printers and disks).

Application developers using pre-release code at level 6.177 may choose to maintain their development environment on 6.177 rather than move to 6.304E. A development environment on 6.304E requires a Developer's Toolkit at level 6.304E.

When this product becomes generally available, it is IBM's intent to additionally:

  • Provide a superior operating environment through system integrity, performance, interoperability, and ease of use when running DOS, Windows, and OS/2 applications
  • Run on Intel 386SX and higher systems.

This booklet describes those product considerations about which you should be aware as you install and use this version of the product. IBM will continue to make enhancements before the product becomes generally available, and we welcome your feedback. This booklet also includes helpful tips and techniques.

We recommend that you read this booklet before installing and using the system.

This document is a supplement to OS/2 2.0 Getting Started, OS/2 2.0 Using the Operating System, OS/2 2.0 Installation Guide, and OS/2 2.0 Quick Reference. If you are migrating from OS/2 Version 1.3 or Windows Version 3.0, we recommend that you read OS/2 2.0 Migrating to the OS/2 Workplace Shell.

Installation

  • If you are installing this version over an earlier OS/2 2.0 level, select the Format your disk during installation option. This process ensures that any earlier-level files will not be left inadvertently on your hard disk. Be sure to back up any files that you want to save before starting the OS/2 2.0 Installation process.
  • If you install this version, you will have to select the Format your disk during installation option when you install the product when it becomes generally available.
  • You do not have to format your disk if you are installing over

OS/2 Version 1.2, OS/2 Version 1.3, DOS, or Windows.

  • When first prompted to restart (reboot) your system after installation, note that the restart can take about 5 minutes, allowing the OS/2 Workplace Shell to initialize itself.
  • If you are installing using a response file, you cannot use the value for Migrate Applications provided in the sample response file. If you wish to migrate existing applications, you must select the Migrate Applications object located in the System Setup folder after OS/2 2.0 has been installed.
  • Be sure, if you install a mouse, that it is connected whenever you start your system.
  • This product supports two display adapters. If the secondary display adapter is an XGA* or 8514/A adapter, it will run in VGA mode.
  • Specific small computer systems interface (SCSI) adapter support for selected SCSI adapter interfaces is included. The device drivers which produce this support are installed in your \OS2 directory, as follows:

SCSI Adapter Filename (in \OS2 Directory)

  • Adaptec 152x AHA152X.ADD
  • Adaptec 154x AHA154X.ADD
  • Adaptec 164x AHA164X.ADD
  • Future Domain TMC-8xx FD8XX.ADD
  • Future Domain TMC-16xx FD16-700.ADD
  • Future Domain MCS-600 FD16-700.ADD
  • Future Domain MCS-700 FD16-700.ADD
Note
For the Future Domain TMC-8xx series, the BIOS must be enabled in order for these 8-bit adapters to function.

You can manually install this support by adding a BASEDEV=filename statement into CONFIG.SYS. For example, if you have an Adaptec 1542 SCSI adapter in your system, you can install OS/2 support by including the statement BASEDEV=AHA154X.ADD at the end of your CONFIG.SYS file. Make sure you do not include a drive letter or path in this statement.

The CONFIG.SYS statement BASEDEV=IBMINT13.I13, included in the CONFIG.SYS file (by default), replaces the DSKBIOS1 function. No special action is required to use any other SCSI hard files. They are supported through the IBMINT13 generic DASD device drivers.

Product Considerations

IBM will continue testing and enhancing this product before it becomes generally available, and we welcome your feedback.

It is our intent to address the limitations described in this Product Considerations section before this product becomes generally available. Where available, we have provided temporary work-arounds.

Performance

IBM strongly recommends that you do not use this version of the OS/2 2.0 product for performance benchmarking. We will continue to improve performance before the product becomes generally available.

IBM's performance objectives for the OS/2 2.0 product are to run DOS and Windows applications equal to or better than they run in their native environments and to run OS/2 applications equal to or better than they run on OS/2 Version 1.3. Based on IBM's measurements of application performance on this version of the product, IBM believes that from a user's perspective, on balance, these performance objectives have been met.

Users may experience slower response times when using some system functions, such as loading programs, starting sessions, and switching between sessions. A minimum of 6MB of system memory will improve performance.

OS/2 Workplace Shell

  • The OS/2 2.0 product was designed for use with a mouse. We recommend that you operate the system with a mouse to ensure consistent results.
  • In some instances, Help is not available from the Help push button or the F1 key. Refer to the Master Help Index for help on specific topics.
  • Copying a folder containing program objects onto a diskette appears successful, but if you try to start or copy the programs from diskette onto another system under this version of the product, the program objects will not be present. (When the OS/2 2.0 product becomes generally available, program objects will not be allowed to be dropped on diskettes).
  • The pop-up menu for multiple-selected items does not always display the actions that are common to all the selected objects.
  • The size and position of some windows may not be restored after you restart your system.
  • Program objects started from command files must have the proper .BAT or .CMD extension specified.
  • Copying a read-only folder into another folder creates two folders.
  • Displaying an object in Details view does not always display current information about the object. The last access and modification dates may not be current. The column titles may be displayed for file-type objects when none are present in the folder.
  • The hard-disk icon in the Drives folder represents tape drives and CD-ROM drives in addition to hard disks.
  • The Undo option on the Associations page in the Settings notebooks for a Program object and the Color Palette object are not operational.
  • On systems with an XGA adapter connected, you must close each section of the Tutorial before moving to the next section.
  • The Special Needs page of the Keyboard object has limited customization capabilities.
  • Make sure you select Shut down before you turn off your computer or you might lose data or the position of your icons.
  • The Settings notebook for "System" in the System Setup folder has two pages with a "window" tab. The page with the radio buttons for Animation should be used. The other page will be removed.
  • If any objects, including folders and programs, are open and running when the system is shut down, only those that were started directly from the desktop will restart when the system is restarted.

To ensure that an object automatically starts when the system is restarted, move the object from its original folder to the desktop. Then, if the object is open when the system is shut down, it will start the next time the system is started.

Desktop Customization

  • If you customize your OS/2 2.0 Desktop to OS/2 1.3 or Windows 3.0, we recommend you read Migrating to the OS/2 Workplace Shell to understand the usability features of your new desktop. The book explains how to make OS/2 2.0 look like OS/2 1.3 or Windows 3.0.

DOS Support

  • When you start a specific version of DOS from a diskette, be sure to insert the diskette in the drive before you start the session.

Windows Support

  • Before cutting and pasting to the OS/2 system clipboard from or to Windows programs, you must start the Clipboard Viewer located in the Productivity folder.
  • Bit maps and metafiles greater than 200KB in size will not be transferred successfully to the public clipboard.
  • Before running WIN-OS/2* in real mode, reset the DOS setting EMS_ MEMORY_ LIMIT to 0 for the VDM to be used.
  • If you choose to copy an existing Windows desktop configuration, it may be necessary to change the MOUSE.DRV statement in SYSTEM.INI. If you are currently using a mouse that creates a statement other than MOUSE.DRV=MOUSE.DRV in the boot.description section of the C:\OS2\MDOS\WINOS2\SYSTEM.INI file (where C: is the startup drive), you will need to change the statement to read MOUSE.DRV=MOUSE.DRV
  • Be certain that Windows applications have completed their initialization before switching back to the OS/2 desktop.

OS/2 Printing

  • Ensure that all print job settings notebooks are closed before closing a print object icon or detail view.

Numeric Coprocessor Emulation

This version of the product will include a numeric coprocessor emulator for use in machines that do not have a numeric coprocessor installed. Currently, we are continuing to improve the accuracy of the results obtained from this emulator. The results obtained from the emulator provided in this version of the product may contain errors and cannot be guaranteed.

Examples of computations which may lead to erroneous results are those involving high-precision operations, operations combining high-precision operands, boundary conditions such as very large or very small quantities, rounding, and underflow.

If you intend to use floating-point operations in mission-critical applications, you must use an 80387 math coprocessor. Installation of an 80387 math coprocessor requires a stepping level of B1 or higher on the 80386 microprocessor.

If you are in doubt about whether your application uses floating-point operations, contact the application vendor.

Local Area Network Support

  • Opening a network group folder in a tree may be slow if your network contains many servers. It is recommended that you use icon view instead.
  • The network folder cannot be moved from the desktop.
  • The *Alias server folder displayed by LAN Server 2.0 is not functional.
  • If you are a LAN Server Network Administrator, do not change the printer configuration on a server once it has been shared.
  • If you log in as a LAN Server Network Administrator and some functions are not available, display the pop-up menu and select Refresh. The administrator functions are now available.
  • Occasionally, the pop-up menu of a network object might show login when you are already logged in, or logout when you are already logged out. Click on login/logout and redisplay the pop-up menu.
  • In this version, do not attempt to access DOS LAN requesters from WIN-OS/2 when you are running a specific version of DOS in a DOS session.

Refer to Product Supplemental Information for LAN Server Version 2.0 for current information regarding network support.

Peripheral Devices

  • When using your Logitech mouse when running in standalone DOS, you may experience problems with your mouse under OS/2. If so, unplug and then plug in your mouse, or, after shutdown, power down and then power up your system.
  • When using the COM port on a PS/2* Model 90 or 95 with Enhanced set to ON, be sure that the Serial Transmit and Serial Receive Arbitration Levels in the hardware configuration are set to Dedicated, with different numbers specified.

For example, when the Serial Port is set to SERIAL 2 in the hardware configuration, its corresponding Serial Transmit Arbitration Level should be set to DEDICATED 3. The Serial Receive Arbitration Level must be set to DEDICATED 4. When both levels of a serial port are set to Shared, data communication and printing from the COM port with Enhanced set to ON will not operate properly. Run the Setup/Diagnostics diskette and follow the instructions on the screen to change your hardware configuration.

  • The OS/2 2.0 product has been designed to allow most DOS and Windows applications to run more reliably than in their native environments.

One or more DOS applications typically can be run concurrently in windows while in the background, although there are some performance trade-offs when DOS graphics applications are run in a window. To realize the full benefits of the OS/2 2.0 product, run these applications in full-screen sessions.

There are three cases in which DOS graphics applications may be suspended (receive no processor time) when running in the background:

  • In the first case, a DOS multiplane application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended, regardless of the graphics adapter installed, if any other DOS application is running in the foreground in a full-screen session.
  • In the second case, a multiplane DOS application that uses advanced graphics, such as 640x480x16 or 640x350x16, will be suspended when a Presentation Manager session is running in the foreground in XGA mode. Currently, this situation occurs even if you have an Extended Graphics Array (XGA) and a Video Graphics Array (VGA) adapter connected to your system.
  • In the third case, a multiplane DOS application that uses 1024x768x16 graphics mode will be suspended when a Presentation Manager session is running in the foreground in 8514/A mode.

Note that suspending DOS applications running in the background generally poses no problem unless the applications are timing-dependent, such as communications or process-control applications. In these cases, suspending them may cause them to fail. Avoid this situation by running these applications in the foreground in full-screen sessions only. If they are graphics applications, run them only in a single-plane mode, such as 640x200x2, 320x200x256, or 640x480x2, in full-screen sessions.

Note also that for WIN-OS/2 sessions, set the VIDEO_ SWITCH_ NOTIFICATION DOS setting to ON to avoid having Windows programs suspended when running in the background.

Personal Computer Manufacturers - Compatibility

The following list depicts those Personal Computer Manufacturers' systems that have passed IBM's compatibility test with the current OS/2 2.0 EEP product. IBM's compatibility test verifies (18) key functions of the OS/2 2.0 operating system. These test results are based on selected model configurations provided by the PCM to IBM. This list is preliminary, and IBM will continually update the list as we proceed with our testing. Current information will be disseminated on various electronic forums and bulletin boards.

  • ACER 1125E
  • ALR BusinessSTATION
  • ALR BusinessSTATION
  • ALR BusinessVEISA 486/33
  • ALR BusinessVEISA 386/33
  • ALR MPS Modular 386/33
  • ALR MPS Modular 486/33
  • ALR POWERPRO 33/486
  • ALR PowerFlex 20X
  • ALR PowerFlex Flyer
  • AMAX PC/486-33
  • APRICOT LS 386SX-20 w/cache
  • APRICOT Qi 486-25
  • AST Premium II 486SX/20
  • AST Premium II 386/33
  • AT&T SAFARI NSX/20
  • COMPAQ DESKPRO 386/25E
  • COMPAQ DESKPRO 386/S
  • COMPAQ SYSTEMPRO EX0-2904D-B1 Model 3002
  • COMPAQ DESKPRO
  • COMPAQ SYSTEMPRO EX0-2804-000L Model 3000
  • COMPAQ 486/50L
  • COMPUADD 320SC Model 486SX/20 Model 101 A002
  • COMPUADD 325 Model 386DX Model 1 A000
  • COMPUADD 333T Model Model 101 A005
  • COMPUADD 433E Model Model 1 A005
  • CUMULUS GLC 486DX/33
  • CUMULUS 486SX/20
  • CUMULUS GLC 386SX/20 Model SMP 128/150
  • CUMULUS GLC 386DX/25
  • CUMULUS GLC 386DX/33
  • DELL PowerLine 433DE
  • DELL System 320SX
  • DELL System 333D
  • DELL System 486D/25
  • DELL System 325P
  • DELL System 320N+
  • DYNEX 386-25
  • EVEREX 486/33E 386/25M EX0-2904D-01EL
  • EVEREX 486/33
  • EVEREX 386/33
  • GRID GRIDCASE 1550sx
  • GRID MFP/420s
  • GRID 386sx/MFP20 XP2670
  • HERTZ 486/33
  • HEWLETT PACKARD Vectra 32MCA 386/25
  • HEWLETT PACKARD Vectra 32MCA RS/25C
  • HEWLETT PACKARD Vectra 486/33T
  • INTEL LP386SX/20
  • MEMOREX-TELEX Model 8267
  • MEMOREX-TELEX Model 8290
  • NCR SYSTEM 3300/3421 Model 2014
  • NCR SYSTEM 3300/3432
  • NCR SYSTEM 3300/3433
  • NCR SYSTEM 3400 Model
  • OLIVETTI M300-10 Model
  • OLIVETTI P750 Model
  • REPLY D32-486-250 Model
  • REPLY D32-386-330 Model
  • REPLY 486-33
  • SAMSUNG DeskMaster 386S/25
  • SIEMENS NIXDORF PCD-3Msx/20
  • SIEMENS NIXDORF PCD-3Bsx
  • TATUNG TCS8640S
  • TATUNG TCS8800D
  • TATUNG TCS9600T
  • TOSHIBA T3100SX Model 1000
  • TOSHIBA T5200/100
  • ZENITH Data Systems Model 2000 Z-486SX/25E
  • ZENITH Data Systems 3000 Z-486/33E
  • ZEOS 386DX-33CT XP2655
  • ZEOS 386SX-208DT
  • ZEOS 486DX-33T

Note: The compatibility test information provided herein is provided for information purposes. IBM MAKES NO

WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE OPERATION OF THE PERSONAL COMPUTERS LISTED.

  • In order for microchannel systems with ESDI hard disks to operate properly:

1. On OS/2 Diskette 1, rename ABIOS.SYS to ABIOS.HLD.

2. Create a null file called ABIOS.SYS. For example:

 COPY CON: ABIOS.SYS
 blank space
 Enter
 PF6
 Enter

3. Begin your installation.

  • An ABIOS timing condition between OS/2 2.0 and the ALR MPS systems can occur during operation. To ensure this condition is not encountered, IBM and ALR have agreed to a temporary solution. The following change should be made to the CONFIG.SYS file on Installation Diskette 1 and after installation, ensuring that the same change appears in the CONFIG.SYS file on the hard disk.

Change BASEDEV=IBM1FPLY.ADD to BASEDEV=IBM1FLPY.ADD /PS2

and

Change BASEDEV=IBM2FLPY.ADD to rem BASEDEV=IBM2FLPY.ADD After Installation Diskette 4:

  1. Put the Installation Diskette in drive A.
  2. Reboot.
  3. Continue until Diskette1 introduction.
  4. Escape (Esc) from Diskette1 to the A: prompt.
  5. Make the same change to C:\CONFIG.SYS.
  6. Copy IBM1FLPY.ADD to C:\OS2 directory.
  7. Remove the diskette.
  8. Reboot and continue the installation.

Tips and Techniques

  • You can improve the performance of some applications by adjusting the DOS settings. If the application does not use extended or expanded memory, these values can be set to zero:
  • IDLE_ SENSITIVITY
  • EMS_ MEMORY_ LIMIT
  • XMS_ MEMORY_ LIMIT.

For more information on DOS settings, refer to the OS/2 2.0 online Master Help Index.

  • If you want to use the asynchronous communications device interface (ACDI) support in the OS/2 2.0 mini-application called PM Terminal, you must edit your CONFIG.SYS file and then restart your system. For IBM PS/2 computers, install the SASYNCDB.SYS driver:
DEVICE=C:\OS2\APPS\SASYNCDB.SYS

For 80386 compatibles, install the SASYNCDA.SYS driver:

 DEVICE=C:\OS2\APPS\SASYNCDA.SYS

When files are transferred to or from a drive other than drive C in PM Terminal, the dialog box may not display all the subdirectories. To correct this problem, select the C drive and then reselect the correct alternative drive.

  • Using the OS/2 Enhanced Editor:
  • The maximum line length is 237 characters.
  • When naming your files, you are unable to use blanks and some nonalphanumeric characters, such as double quotes, apostrophes, and brackets.
  • The FIND option in the OS/2 System Editor does not display the results of a search. To view these results, press Alt+F6 to move the focus from the Find dialog box to the text entry area.
  • We have improved the high-performance file system (HPFS) by adding new options that users can specify. Also, we have improved both the HPFS and the File Allocation Table (FAT) file systems by expanding the read-ahead logic for small-record input/output (I/O) of less than 512 bytes in size. These enhancements are expected to provide faster performance when sequential reads are performed.

Use the IFS= statement to define the maximum I/O record size that can be cached using the HPFS.

  • By default, 2MB is the amount of memory allocated to each WIN-OS/2 session. Currently, we recommend 2MB for each WIN-OS/2 session you plan to run.

If you receive an error indicating that your WIN-OS/2 session has insufficient memory, you can try adjusting the memory to 3MB or 4MB. However, this setting should not be set high arbitrarily because the OS/2 swap file (SWAPPER.DAT) will be allowed to grow in proportion to the amount of additional memory you allocate.

The optimum size of the swap file is relative to your environment. If the swap file is located in its own partition, it is preferable to be conservative when you specify the size of that partition. These specifications may be helpful.

 4MB system : 7 to 12MB
 6MB system : 5 to 10MB
 8MB system : 3 to 8MB
  • OS/2 allows you to run a specific version of DOS in a DOS session along with the OS/2 2.0 product. This feature helps to ensure compatibility with applications, such as block device drivers, that otherwise would be incompatible with the OS/2 2.0 environment. Currently,
  • If you have already started a version of DOS from a diskette, you will not be able to start another version of DOS from your hard disk.
  • You may experience problems when starting, or booting, DOS from your A drive or from other drives.
  • You cannot start multiple copies of a specific version of DOS using a single image. To make multiple images, create them on your hard disk using the VMDISK.EXE utility located in the \OS2\MDOS\ directory. Change the DOS_ STARTUP_ DRIVE DOS setting to start from the image you created.
  • When asked to specify a directory from which to add fonts, do not specify the C:\OS2\DLL path, where C: is your startup drive.

Applications Considerations

Temporary Limitations

IBM has tested many DOS, Windows and OS/2 applications. Most of them run unchanged, but some require special attention when running on this version of the product. IBM currently plans to address these limitations before the OS/2 2.0 product becomes generally available. Where available, we have suggested temporary work-arounds.

Other Limitations

Some categories of applications, usually because of their design or because they use undocumented interfaces, will not operate properly with the OS/2 2.0 product. IBM is in the process of contacting these vendors about resolving these incompatibilities. Some vendors have already developed a fix and are willing to make the fix available. These have been noted.

These five categories of applications include:

  • Applications that use the DOS Protect-Mode Interface, the Expanded Memory Specification (EMS), or the Extended Memory Specification (XMS) are supported. Other DOS extenders, such as the virtual control-program interface (VCPI), that require exclusive access to the 80386 control registers, are not supported because they could violate the integrity of the system.
  • Functions in applications that directly address the physical sectors to perform write operations are not supported because these operations could violate the integrity of the system.
  • Some Windows applications invoke the Windows mini-applications to run a subset of function. If you did not format your hard disk when you installed this version of the product, and if you already had Windows Version 3.0 installed, these mini-applications will be invoked automatically.
  • Windows applications that require enhanced mode
  • DOS or Windows applications that use undocumented DOS or Windows interfaces

Summary of Applications

Application Result Comment
Ansel DOS program - The program is not operational. See Temporary Limitations on page 18.
AutoCAD OS/2 program - The program does not return from the desktop. Close the program only to a command prompt upon exit. See Other Limitations on page 18.
Auto Manager DOS program - The program cannot be installed if you try to use the version that uses extended memory. Install the real mode version. The program expects COMMAND.COM to be in the root directory of C:\. Copy COMMAND.COM to the C:\ directory from the C:\OS2\MDOS\COMMAND.COM directory.

See Other Limitations on page 18.

Borland C++ 2.0 DOS program - The Turbo C++ extended versions of Turbo Pascal these programs use non-DPMI DOS extenders. Use the standard version.

See [Other Limitations] on page 18.

Central Point Backup DOS program - The program will provide its own graphic fonts when running in a DOS session. Run in a DOS full-screen session. See [Other Limitations] on page 18.
Peachtree Complete III DOS program - The Set the DOS setting, DOS_FILES to 40.

5.0 program requires more than 40 file handles to Temporary run and non standard ASCII characters may be displayed.

See [Limitations] on page 18.

Codeview for Windows Version 3.0 Windows program - The See ]Temporary

program debugger is unable to load a LimitationsØ on page 18. program for debugging.

Distinct Backup Windows program - The Back up to a hard disk.

message See ]Temporary ]Unrecoverable floppy LimitationsØ on page 18. disk errorØ may be displayed when you try to back up to diskette.

Fastback Plus 2.1 DOS program - The program is unable to support backing up to a diskette. Back up to a hard disk.

See [Other Limitations] on page 18.

FastLynx DOS program - The program is unable to establish a connection when VCOM.SYS is installed. Remove the DEVICE=C:\OS2\MDOS\VCOM.SYS statement from the CONFIG.SYS file. If parallel port is used, no problems are encountered.
FormBase 1.2 Windows program - The AUTOEXEC.BAT file is automatically updated with the SHARE statement. Use an editor to remove the SHARE command from the AUTOEXEC.BAT file.
Freelance/G OS/2 program - You will not be able to install some options because the program looks for an earlier version of OS/2 (for example, OS/2 version 1.x). Lotus will provide a fix to install on the OS/2 2.0 product or install under OS/2 Version 1.3.

See [Other Limitations] on page 18.

LapLink III 3.0 DOS program - Your serial ports may not operate properly. Remove the VCOM.SYS and COM.SYS statements from your CONFIG.SYS file.

See [Other Limitations] on page 18.

Magellan DOS program - The UNDELETE functions in the program require physical sector addressing. Use the OS/2 UNDELETE command.

See [Other Limitations] on page 18.

MagiCorp Windows program - Running this program along with other WIN-OS/2 programs in Windows sessions may cause the system to stop. Run this program by itself or try restarting the session.

See [Temporary Limitations] on page 18.

Mathcad Windows program - The program cannot be installed under OS/2. Install under DOS.

See [Temporary Limitations] on page 18.

More Windows Windows program - Full-page splits the screen, and the screen receives a mirror image and then repaints the desktop. Use only the other three white mode modes.

See [Temporary Limitations] on page 18.

MS Bookshelf DOS Multimedia CD-ROM Reference program - The program Library requires the device driver MOUSE.COM Version 6.14 to run. See [Other Limitations] on page 18.
MS Excel OS/2 program - The help index and the help do not operate properly. Avoid using these keyboard functions.

See [Temporary Limitations] on page 18.

MS Money 1.0 Windows program - The program invokes the mini-application called Calculator for computations. Use the Calculator mini-application in the Windows Version 3.0 OS/2 Productivity folder.

See [Other Limitations] on page 18.

Multimedia Extensions DOS program - This Include the installation program program starts its own UseOS2shield=0 for Windows desktop program and statement in your assumes that if it is not the first application SYSTEM.INI file before starting the multimedia loaded, another desktop extensions program. Then is running. reedit the SYSTEM.INI file to say UseOS2shield=1

after you have installed the Windows multimedia extensions and before starting other WIN-OS/2 sessions.

See [Other Limitations] on page 18.

MusicPrinter Plus DOS program - The program cannot be started in a DOS session. Install the program under DOS and run it under OS/2.

See [Other Limitations] on page 18.

Norton Backup 1.2 DOS program - Backing up to diskette may be very slow. See [Temporary Limitations] on page 18.
Norton Desktop Windows program - The program assumes that if it is not the first application loaded, another desktop is running. Include the UseOS2shield=1 statement in your SYSTEM.INI file in the \OS2\MDOS\WINOS2 directory on your start-up drive.

See [Other Limitations] on page 18.

Norton Utilities 5.0 DOS program - The UNDELETE functions in the program require physical sector addressing. Use the OS/2 UNDELETE command.

See [Other Limitations] on page 18.

Omnipage Professional 1.0 Windows program - The program must run in 386 enhanced mode. See ]Other LimitationsØ on page 18.
Oracle DOS program - The program cannot be installed. See ]Other LimitationsØ on page 18.
Paradox 3.5 DOS program - The extended version of the program (PARADOXK.EXE) uses non-DPMI extenders. Use the standard version of the program (PARADOXR.EXE).

See [Other Limitations] on page 18.

Persuasion 2.0 Windows program - Printing from COM1 may produce unexpected results. If the clipboard is set to public, the program is unable to copy to the clipboard. Use LPT1 to print. Deselect the public option on the clipboard.

See [Temporary Limitations} on page 18.

ProComm 2.0 DOS program - The ProComm SHELL command starts the OS/2 shell instead of the DOS shell, and the DOS session stops. Avoid using the SHELL command.

See [Temporary Limitations] on page 18.

Publishers PowerPak Windows program - The 2.1 program does not create the C:\POWERPAK directory because the directory appears to exist. Create the following directory: C:\OS2\MDOS\WINOS2\POWERPAK; then run the installation batch file.

See [Temporary Limitations] on page 18.

Quicken for Windows Windows program - The program invokes the mini-appication called computations. Use the Calculator mini-application in the Windows Version 3.0 OS/2 Productivity folder.

See [Other Limitations] on Calculator for page 18.

SideKick OS/2 program - The Notepad does not operate properly. Install a printer and be sure that it is present on the desktop. Avoid minimizing the Notepad.

See [Temporary Limitations] on page 18.

Smartfax DOS program - The program does not operate properly. See [Other Limitations] on page 18
TAPCIS DOS program - The TAPCIS.HLP file cannot be found. Run FIX_FIND.COM before running TAPCIS. This is a Terminate and Stay Resident program in the OS2\MDOS directory.

See [Temporary Limitations] on page 18.

Wing Commander II DOS program - The program is not operational or runs very slowly in a DOS session. Select the No Sound option during the Wing Commander II installation to improve performance.

See [Temporary Limitations] on page 18.

Wordperfect for Windows Windows program - The program may not operate properly. Find the file WPWINFIL.EXE in the Wordperfect directory and run:
FIXWP \path\WPWINFIL.EXE

For additional information contact Wordperfect at 1-800-228-6076 or 1-800-228-1029.

See [Temporary Limitations] on page 18.

Improvements from the LA Product

Some of the restrictions identified in the LA Product Considerations document have been corrected in this EEP version of the product. These items include:

Installation Improvements

  • A response file can be used to install OS/2 2.0. See the OS/2 2.0 Installation Guide for details.
  • The DSKBIOS1 function discussed in the LA document is now included in the BASEDEV=IBMINT13.I13 CONFIG.SYS statement, by default. No special actions are required to operate SCSI devices.
  • If you select not to install some Productivity and Games programs, blank icons representing these programs will no longer be installed.
  • DOS LAN requesters no longer require that DOS have control of the system. They will run on a booted version in a VDM.
  • The time needed to install the OS/2 has been reduced.

Product Considerations Improvements

OS/2 Workplace Shell

  • You can delete multiple objects individually, or you can delete them all at one time.
  • An icon representing Drive A will appear on the desktop.
Double-clicking on this icon will now provide access to Drive A.
  • The settings notebooks for the Drives objects are now operational when displayed from the object's pop-up menu.
  • Actions performed on fonts no longer produce inconsistent results.
  • The time needed to shut down the system has been reduced.

Windows Support

  • The following items are now described in the OS/2 2.0 online or hard copy documentation:
  • Follow the manufacturer's instructions to install Windows applications under the OS/2 2.0 product. If the installation is unsuccessful, start a full-screen DOS session and try again. Another alternative is to choose Run from the File menu of the WIN-OS/2 Program Manager.
  • To start Windows applications, do one of the following:
  • Install them as separate objects on your desktop.
  • Select Run from the WIN-OS/2 Program Manager.
  • Type WINOS2 followed by the program name in a full-screen DOS or OS/2 session.
Note that you cannot run DOS applications using Run from the File menu of the Program Manager. They must be run from the (OS/2) desktop.
  • OS/2's Dynamic Data Exchange (DDE) feature allows you to dynamically update and change data in one running program and effect those changes in another running program.

Note that before performing DDE between an OS/2 and a Windows application, you must start the Data Update object in the Productivity folder.

  • Not all clipboard and DDE data formats are transferable to the public clipboard or shared between Windows and PM applications.
  • You must run Windows applications in a single WIN-OS/2 session if you are using private Windows data formats.
  • A set of WIN-OS/2 printer drivers is included with this product. When you create an OS/2 printer, you will be asked if you want a Windows-equivalent configuration, if one is available. You also will be asked to install a WIN-OS/2 printer driver.

If a WIN-OS/2 printer is not automatically installed during OS/2 installation, you can install WIN-OS/2 printer drivers from the WIN-OS/2 Control Panel. WIN-OS/2 printer drivers are located on the Printer Driver Diskettes 1-6. If you want to use a Windows printer driver that is not automatically installed by OS/2, or is not shipped with OS/2, configure the Windows printer driver to use an OS/2 port that has the IBMNULL printer driver associated with it. The IBMNULL printer driver is installed during system installation. If IBMNULL is not displayed in the list of available printer drivers, use the Install pop-up menu choice on an existing printer driver to display the Printer Driver Install dialog box. 1. Insert Printer Driver Diskette1 in your diskette drive; then select Refresh. 2. Select IBMNULL from the list; then select Install. 3. Select Cancel; then select IBMNULL for the Printer object. Note that LPT1.OS2 and LPT2.OS2 support better performance than LPT1 or LPT2 when configuring from the WIN-OS/2 Control Panel.

  • Performing DDE between two Windows applications running in separate sessions or between a Presentation Manager (PM) and a Windows application currently no longer cause the Windows application running in the background to be suspended (receive no processor time).
  • If the Windows clipboard is set to public, requests to print the screen from a Windows session (using PrintScreen) are now successful.
  • The contents of the clipboard are no longer lost if you exit from a Windows application during a cut, copy, or paste operation.
  • Bit-map files and metafiles can be converted compatibly between Windows and PM applications when operating in all video modes.
  • To install your Windows LAN device drivers and configure WIN-OS/2 to use these device drivers, run SETUP.EXE from the WIN-OS/2 full screen session.
  • It is not necessary to define a Windows printer if you are installing Windows multimedia extensions under this version.
  • Like Windows, the OS/2 2.0 product automatically installs corresponding Windows mouse and printer drivers when you select a Presentation Manager* mouse driver.
  • On systems with an XGA adapter connected, starting Windows from a full-screen session and then closing the session no longer causes the screen to behave inconsistently.

OS/2 Printing

  • You can now delete any printer device drivers from the Printer object. Doing so no longer causes subsequent attempts to reinstall these drivers to fail.

Peripheral Devices

  • The DOS DISKCOPY command now operates properly when used on an external 5 1/4-inch diskette drive.

Tips and Techniques Improvements

  • The OS/2 mini-application called Cat and Mouse is now operational.
  • Closing a DOS or Windows session from the Window List or from a pop-up menu, while an application is running in that session, no longer causes subsequent attempts (by these sessions) to access devices to fail.
  • HPFS performance for 2KB and 4KB I/O has been improved.
  • All networking applications may now start from the Drives objects.
  • The following items are now described in the OS/2 2.0 online documentation:
  • Adjusting these DOS settings for Windows full-screen objects or other Windows program objects, may boost the performance of applications running in Windows sessions.
KBD_CTRL_BYPASS = CTRL_ESC
This setting allows the WIN-OS/2 Program Manager to recognize a Ctrl+Esc and then display the Task List.
MOUSE_EXCLUSIVE_ACCESS = ON
This setting allows WIN-OS/2 (in place of the PM) to control the Mouse pointer if you run a WIN-OS/2 session in a window.
VIDEO_SWITCH_NOTIFICATION = ON
This setting notifies a DOS program to do its own save and restore of the video state.
VIDEO_8514A_XGA_IOTRAP = OFF
This setting must be set so that DOS and WIN-OS/2 sessions can continue to run when in the background (for systems with 8514/A and XGA adapters only).
  • The performance of DOS applications is optimal when running in full-screen sessions. You can press the Alt+Home keys to run your DOS applications in full-screen DOS sessions.
  • If you are running Windows and have an 8514 Windows video adapter (8514.DRV) installed, do not change the default settings for VIDEO_SWITCH_NOTIFICATION and VIDEO_8514_XGA_IOTRAP.

Applications Considerations Improvements

The following applications, restricted in the LA version of this product, are now supported:

  • Borland C++ 3.0
  • Chipchat
  • Control Room 1.0
  • Crosstalk IV
  • Dynacomm
  • Framework III Version 1.1
  • IBM Current*
  • MS Flight Simulator
  • MS Word for OS/2
  • New Wave 3.0
  • PC3270
  • PC Paintbrush IV
  • PFS First Choice 3.1
  • Superprint 2.0
  • Terminator
  • Winfax Pro 2.0

Disclaimers

Terms denoted by a single asterisk (*) in this booklet are trademarks of the IBM Corporation (IBM) in the United States and/or other countries.

These terms include:

  • Current PM
  • IBM Presentation Manager Operating System/2 PS/2
  • OS/2 Personal System/2
  • XGA WIN-OS/2

Terms denoted by a double asterisk in this booklet (**) are trademarks of other companies. Other trademarks appearing in this booklet are owned by their respective companies.

  • Microsoft, MS Bookshelf, MS Excel, MS Flight Simulator, MS Money, and Windows are trademarks of Microsoft Corporation.

IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.

Copyright IBM Corporation, 1992, all rights reserved.