Mega Demo/MegaDemoCDRom1.cdr/info/readme.inf

OS/2 Help File | 1992-07-09 | 87.8 KB | 2,108 lines

ΓòÉΓòÉΓòÉ 1. OS/2 2.0 README ΓòÉΓòÉΓòÉ

In OS/2* Version 2.0, IBM* performed the most comprehensive testing ever done
on any version of the OS/2 operating system.  This included extensive DOS,
Windows**, and OS/2 application compatibility validation in addition to stress,
usability, and performance testing.  While most users will not require the
information in this README, it contains unique application compatibility
information and other useful tips and techniques that might be helpful in
specific situations.  Some of the information is intended for the more advanced
user or for the user already familiar with various functions provided with OS/2
2.0.

The information was largely collected during the final comprehensive system and
compatibility testing phases, which involved over 30,000 users of early
versions.  It was not finalized before the publications were printed and we
want to share this information with you.

If you want to search for a specific topic, click on "Search" on the button bar
below.  For more information about searching, and for other help related to the
Information Presentation Facility, click mouse button 1 on "Help", then click
on "Help Index."

The scope of this information includes:

o Service and Support Information

o Installation

o OS/2 Workplace Shell

o Application Compatibility

o Performance

o Windows Version 3.0 Programs Support

o Video/Graphic Support

o Hardware Considerations


ΓòÉΓòÉΓòÉ 2. Service and Support Information ΓòÉΓòÉΓòÉ

OS/2 2.0 users can access electronic support for current technical information
and exchange messages with other OS/2 users, 24 hours a day.  If you run into
problems or simply need a question answered about OS/2 2.0, there are two ways
to get help electronically:  the new IBM BBS (Bulletin Board System) and
CompuServe.

For information about registering for and accessing the IBM OS/2 BBS, call
1-800-547-1283.

For CompuServe membership information, call 1-800-848-8199 and ask for
representative 239.

If you already are a CompuServe member, simply type "GO IBMOS2" at the ! prompt
to access the IBMOS2 forum.


ΓòÉΓòÉΓòÉ 3. Installation ΓòÉΓòÉΓòÉ

o After installation, and before you run any DOS or Windows program, we
  recommend you shut down your system.

o Support for the High Performance File System (HPFS) was not added to your
  system if you installed OS/2 2.0 using either "Install all features" or
  "Install preselected features," and your system:

   - Has 6MB or less of memory, and
   - Did not previously have HPFS support.

  To install HPFS support, use the Selective Install object in the System Setup
  folder.

o If you select "Automatically update CONFIG.SYS and AUTOEXEC.BAT," some
  device-driver statements might not be copied to your new CONFIG.SYS file with
  a REM statement as stated in the "Installation Guide."  Select instead, "User
  edit CONFIG.SYS and AUTOEXEC.BAT" to copy these device drivers to your new
  CONFIG.SYS file.

o The SETBOOT utility program supports an immediate-restart function that will
  restart the system to the specified drive without going through the Boot
  Manager Menu.  The parameter is /IBD:DRIVE, where "DRIVE" is the letter of a
  startable partition (for example, SETBOOT /IBD:E).  This example would start
  the logical drive E without displaying the Boot Manager Menu.  If the Boot
  Manager is not present, then only drive C can be specified.

o If you are using Boot Manager, and one of your partitions contains OS/2
  Version 1.3 with Dual Boot, copy BOOT.COM from the OS/2 2.0 \OS2 subdirectory
  to the OS/2 1.3 \OS2 subdirectory.

o To enable the UNDELETE command, delete "REM" from the beginning of the
  following statement in the CONFIG.SYS file:

    REM SET DELDIR=

o To use the ACDI support provided by PM Terminal, delete "REM" from the
  beginning of the following statement in the CONFIG.SYS file:

    REM DEVICE=d:\OS2\APPS\SASYNCDx.SYS

  where "d:" is the drive and "x" is either A or B.

  Then restart your system.

  If you selected the PM Terminal program with either "Select features and
  install" or the Selective Install object in the System Setup folder, the ACDI
  support is activated and you do not need to change the CONFIG.SYS file.

o Following is additional information for the "Copying the Response File to a
  5-1/4 Diskette" section of Chapter 5 in the "OS/2 2.0 Installation Guide."

   If you are installing OS/2 2.0 in a non-Micro Channel computer:

      - Delete the following additional files from Installation Diskette 1:

                IBM2*.ADD
                *O2.SYS

      - Delete the following from the CONFIG.SYS file:

                BASEDEV=IBM2FLPY.ADD
                BASEDEV=IBM2ADSK.ADD
                BASEDEV=IBM2SCSI.ADD

   If you are installing OS/2 2.0 in a Micro Channel computer:

      - Delete the following additional files from Installation Diskette 1:

                IBM1*.ADD
                *01.SYS

      - Delete the following from the CONFIG.SYS file:

                BASEDEV=IBM1FLPY.ADD
                BASEDEV=IBM1S506.ADD

o IBM's testing of a beta Windows Version 3.1 environment indicates that the
  OS/2 2.0 Installation program will not configure your WIN-OS/2 desktop.  If
  the Windows directory that is found is from a Windows Version 3.1
  environment, either change the DOS PATH to point to a Windows Version 3.0
  environment, or select the default environment.

o If you have configured your system for a touch device, the System
  Configuration window in the Selective Install program will incorrectly show
  "PS/2 Style Pointing Device" as the default mouse selection.

  To change a touch device to a different pointing device, select "Mouse" on
  the System Configuration window, and then select the pointing device you want
  to use.  Finally, select the OK push button.

o Occasionally, the Migrate Applications program might not find all
  applications.  In this case, retry the Find Programs operation.


ΓòÉΓòÉΓòÉ 4. OS/2 Workplace Shell ΓòÉΓòÉΓòÉ

o Because of device-resource limitations, when too many applications are open,
  or when too many bit maps are visible on the screen, new icons, tabs, or
  other bit maps might not be drawn.  You can fix this situation by closing
  unused folders and applications so their device resources can be used by
  other processes.

o In certain low resource situations, the final shutdown message might not
  appear after a shutdown is performed.  To ensure that shutdown has completed,
  wait until all disk activity stops before powering down or restarting your
  computer.

o If you change the title of an object from within the Find Results folder, the
  name of the original object will be changed.

o If you formatted your installation drive with HPFS, you might not be able to
  access files in the Desktop folder from DOS or Windows applications.

o In the Help information for Find, disregard any references to page 2.

o If you encounter a situation in which you cannot restart the operating
  system, press and hold the left Ctrl, left Shift, and F1 keys. This disables
  the automatic program startup feature of the desktop.  Press and hold the
  keys when the white screen first appears and hold them down until the icons
  appear on the desktop.

o If you start the operating system and you do not see some of the system icons
  (such as OS/2 System or Shredder), there is a function that will allow you to
  reset the desktop to its default configuration.

    WARNING:
  USING THIS FUNCTION WILL REMOVE ANY DESKTOP CUSTOMIZATION YOU HAVE DONE SINCE
  YOU INSTALLED THE OPERATING SYSTEM.

   To perform this function, do the following:

    1. Restart the computer.

    2. Before the first OS/2 Logo panel appears, hold down Alt+F1 for 20
       seconds.

  When the operating system was installed, certain system files (CONFIG.SYS,
  OS2.INI, and OS2SYS.INI) were placed in the \OS2\INSTALL subdirectory.  When
  you perform the recovery function described above, the current versions of
  those files are automatically renamed and are replaced by the default
  installation versions.  If you have a STARTUP.CMD file, that file is also
  renamed, causing the startup feature to be deactivated.

o If you were previously using the OS/2 2.0 Limited Availability version and
  you installed OS/2 2.0 without reformatting, you might not be able to delete
  existing associations.  If this occurs, make a copy of the program object and
  discard the original.

o If you were previously using the OS/2 2.0 Limited Availability version and
  you installed OS/2 2.0 without reformatting, you must update the path and
  file name of

   - OS/2 System Editor to \OS2\APPS\E.EXE
   - Clipboard Viewer to \OS2\APPS\CLIPOS2.EXE

Related Information:

o Printing from the OS/2 Workplace Shell


ΓòÉΓòÉΓòÉ 4.1. Printing from the OS/2 Workplace Shell ΓòÉΓòÉΓòÉ

o If you plan on using an HP PaintJet printer to print bit maps, make sure you
  set the printer-specific format check box in the queues option of the printer
  object.

o If you are going to install the HP LaserJet printer driver over an existing
  driver, be sure to delete all the old *.FNT files FIRST. You can do this by
  deleting the printer driver from the Workplace Shell printer object and
  responding "Yes" when asked if the driver files should be deleted from the
  hard disk.

o If you use the "print while spooling" printer-object setting, and your
  printer stops printing, close the job that was printing.

o To improve the performance of viewing a network printer object, use a long
  refresh interval or set the interval to 0 (no refresh).

o If you move the network object from the desktop to another folder, the
  network printer object template will not appear the next time you start the
  system. To make it reappear, move the network object back to the desktop and
  restart the system.

o If you delete a printer definition, use the Delete option of the pop-up menu.


ΓòÉΓòÉΓòÉ 5. Application Compatibility ΓòÉΓòÉΓòÉ

Most DOS, Windows, and OS/2 programs run under OS/2 2.0 without any
modification.  A few need specific attention, such as changes to DOS settings,
for optimum performance.  Some categories of programs, however, do not work
correctly with OS/2 2.0 because of their design, or because they use
undocumented interfaces, or because they perform restricted activities.  The
following list identifies these categories of programs.

 1. DOS extenders that require exclusive access to the 80386 control registers,
    such as the Virtual Control Program Interface (VCPI), are not supported
    because they would violate the integrity of the system.  The DOS
    Protect-Mode Interface (DPMI 0.9), the Expanded Memory Specification (EMS),
    and the Extended Memory Specification (XMS) are supported.

 2. Programs that directly address the physical disk sectors to perform
    disk-write operations are not supported.  These operations would violate
    the integrity of the system.  This category includes most DOS UNDELETE
    programs.

 3. Some Windows programs make use of the Windows accessory programs, like the
    Calculator.  If you already had Windows Version 3.0 installed and you did
    not format your hard disk when you installed OS/2 2.0, the accessory
    programs are on your hard disk and are supported by OS/2 2.0.  However, the
    accessory programs are not part of the WIN-OS/2 environment included with
    OS/2 2.0.

 4. Programs (and hardware) that require the Windows Enhanced mode are not
    supported.  This mode uses an unsupported memory-management method.
    Programs that run in the Windows Standard mode and Real mode are supported.

 5. Programs that manipulate the 80386 control registers, such as 386 DOS
    debuggers, are not supported; this would violate system integrity.

 6. The following fax boards and programs contain timing sensitivities that
    might prevent reliable operation:

   o ATI ETC
   o Cardinal FAX
   o Practical Peripherals
   o Smart Fax
   o Twincomm 24/96

 7. For more reliable DOS communications performance on slower systems, the
    combined baud rate should not exceed 9600 bps for one or more concurrent
    DOS applications.

Our testing has identified the following programs that perform one or more of
the activities described above.

o Ansel for Windows
o Bound Checker (DOS)
o Central Point Backup for Windows
o Close-Up (Windows)
o Desert Storm CD-ROM (Windows)
o Distinct Back-Up (Windows)
o DoDot 3.0 (Windows)
o Fax Concentrator (DOS)
o Magic-CV (DOS)
o Mathematica 2.0 (Windows)
o MusicPrinter Plus 4.0 (DOS)
o OmniPage Professional 1.0 (Windows)
o Oracle (DOS) (There is an OS/2 version of this program.)
o Perceive for Windows
o Realizer 1.0 (Windows)
o Sherlock Holmes CD-ROM (DOS)
o Smart Fax (DOS)
o Soft-ICE (DOS)
o Splash 1.01 (DOS)

In addition to the restricted activities described previously, some general
conditions you should be aware of are in the following list:

o Some DOS and Windows programs run correctly only in full-screen sessions.
  Any Windows program that does not use the Windows API to change the video
  mode should be run in a WIN-OS/2 full-screen session.

o Some DOS and Windows programs must be installed or run in a "Specific-DOS"
  session; that is, in a session that was started by booting from an actual
  version of DOS.

o Some programs run in OS/2 DOS or WIN-OS/2 sessions, but require that you
  install the program under DOS.

o Windows programs cannot start DOS sessions or DOS programs.

o DOS programs that use low-level file system calls cannot access HPFS disks.

o Code-page switching support is not available for graphics mode in DOS
  sessions.

o Some DOS and Windows programs use security keys as protection against
  copyright infringement.  The security key is a 25 pin connector that is
  connected to the parallel port of the computer on which the program is
  executing.  The program checks to see if the connector is attached and, if
  the connector is not present, the program is assumed to be an illegal copy.
  When more than one DOS session is running one of these programs, a SYS1799
  error can result.  This occurs because the programs that use these security
  keys do not de-allocate the parallel port if a second session is started for
  a program that also requires the security key.  This error is the result of a
  direct I/O parallel port contention mechanism that protects the user from
  possible data corruption.  To disable this mechanism press Ctrl-Alt-PrtSc
  while the DOS session that first performed direct I/O to the parallel port
  has the keyboard focus.

o If your Windows Multimedia Extension programs do not work correctly after
  being migrated to OS/2 2.0, re-install them under WIN-OS/2.

The following list provides information about the compatibility of specific
programs with OS/2 2.0. This information is version-specific; later versions of
the same program might operate correctly.  Some program manufacturers already
have resolved incompatibility issues and have fixes available; these are noted.

Action! Sampler 1.0 (Windows)
Adobe Type Manager (Windows)
After Dark (Windows)
Aldus Pagemaker 4.0 (Windows)
Aldus Persuasion 2.0 (Windows)
Arts & Letters Graphics Editor 3.1 (Windows)
AutoCAD Version 10 (DOS)
AutoCAD (OS/2)
AutoManager 4.0 (DOS)
Borland C++ 2.0 (DOS)
Central Point Backup for DOS 7.1 (DOS)
Central Point PC Tools Deluxe 7.1 (Windows)
Commander Keen (DOS)
Control Room 1.0 (DOS)
CorelDRAW 2.0 (OS/2)
CorelDRAW 2.0 (Windows)
CorelDRAW 2.1 (Windows)
dBase IV 1.1 (DOS)
Designer (OS/2)
Drafix CAD Version 1.11 (Windows)
Drafix CAD Version 3.0 (Windows)
Dynacomm Asynchronous OS/2 (OS/2)
Enhanced Editor (OS/2)
F19 (DOS)
F-117A Stealth Fighter 2.0 (DOS)
Fastback Plus 2.1 and 3.04 (DOS)
FastLynx 1.1 (DOS)
FormBase 1.2 (Windows)
Form Publisher (Windows)
FotoMan (Windows)
Framework III 1.1 (DOS)
Harvard Graphics (Windows)
Harvard Draw (Windows)
hDC FileApps 1.0 (Windows)
HP New Wave 3.0 (Windows)
IBM 3363 Optical Disk Drive*
IBM PC/3270 V2.0* (DOS)
IBM PC/3270 V2.0* (Windows)
Intel SatisFAXtion
King's Quest (DOS)
LAN Support Program Device Drivers (DOS)
LANtastic 4.1 (DOS)
LapLink III 3.0 (DOS)
Linkway Mammals (DOS)
Linkway Presidents (DOS)
Lotus 123 for Windows 1.0 (Windows)
Lotus Freelance Graphics for OS/2 (OS/2)
Lotus Freelance Graphics for Windows (Windows)
Lotus Magellan 2.0 (DOS)
Lotus Notes (OS/2)
MagiCorp (Windows)
Mathcad 3.0 (Windows)
MicroProse Civilization (DOS)
Microsoft Bookshelf - CD-ROM Reference Library** (DOS/Multimedia)
Microsoft Chart 3.0** (DOS)
Microsoft Codeview** (DOS/OS/2)
Microsoft Codeview for Windows Version 3.0** (Windows)
Microsoft Excel for DOS 2.1** (DOS)
Microsoft Excel for OS/2 3.0** (OS/2)
Microsoft Excel for Windows 3.0** (Windows)
Microsoft Money 1.0** (Windows)
Microsoft QuickC** (Windows)
Microsoft Project for Windows 1.0** (Windows)
Microsoft Windows 3.0** (DOS)
More Windows (Windows)
National Geographics Mammals (DOS)
The Norton Backup 1.2 (DOS)
The Norton Desktop (Windows)
The Norton Utilities 5.0 (DOS)
PaintShow Plus 2.21 (DOS)
Paradox 3.5 (DOS)
Peachtree Complete III 5.0 (DOS)
Perform Pro 1.0 (Windows)
PFS: First Choice (DOS)
PFS: WindowWorks 1.75 (Windows)
Photostyler (Windows)
Publisher's PowerPak  2.1 (Windows)
Quattro Pro 3.0 (DOS)
Quicken (DOS)
Quicken for Windows (Windows)
Risk (DOS)
SantaFe Media Manager (DOS)
SideKick (OS/2)
Signmaster 5.11 (DOS)
Soft Term (OS/2)
SoundBlaster (DOS)
Space Quest IV (DOS)
SQLWindows 3.0 (Windows)
Turbo C++ 2.0 (DOS)
Turbo Debugger 2.01 (DOS)
Turbo Debugger for Windows (Windows)
Turbo Pascal 6.0 (DOS)
The Way You Work (DOS/Windows)
Windows Multimedia Extensions (Windows)
WINFAX PRO (Windows)
Wing Commander II (DOS)
WordPerfect for Windows (Windows)
WordPerfect Office 3.0 (DOS)
Xtree Pro Gold 2.0 (DOS)


ΓòÉΓòÉΓòÉ 5.1. Action! Sampler 1.0 (Windows). ΓòÉΓòÉΓòÉ

o The DPMI_MEMORY_LIMIT WIN-OS/2 setting must be set to 5 or greater.


ΓòÉΓòÉΓòÉ 5.2. Adobe Type Manager (Windows) ΓòÉΓòÉΓòÉ

o When using an IBM 4029* printer in PPDS mode with Adobe Type Manager, some
  Windows programs may not function correctly.  If this occurs, do not use the
  printer resident fonts.  To disable printer resident fonts, bring up the
  control panel of the Windows Adobe Type Manager and ensure that the selection
  "Use Pre-built or Resident Fonts" is disabled.


ΓòÉΓòÉΓòÉ 5.3. After Dark (Windows) ΓòÉΓòÉΓòÉ

o To run in a WIN-OS/2 window, change the object's settings to hide or minimize
  the icon to the desktop.


ΓòÉΓòÉΓòÉ 5.4. Aldus Pagemaker 4.0 (Windows) ΓòÉΓòÉΓòÉ

o The spelling checker cannot locate the dictionary.

o Deselect the public setting to use the clipboard.

o If you experience incorrect output when spooling Standard format files to the
  printer, set the printing to RAW mode.  To do this, take the following
  actions:

    1. Go to the Printer icon on the desktop

    2. Select Open, then Settings, then Queue Options.

    3. Ensure that Printer Specific Format is checked.


ΓòÉΓòÉΓòÉ 5.5. Aldus Persuasion 2.0 (Windows) ΓòÉΓòÉΓòÉ

o Use the parallel ports to print.

o Deselect the public setting to use the clipboard.


ΓòÉΓòÉΓòÉ 5.6. Arts & Letters Graphics Editor 3.1 (Windows) ΓòÉΓòÉΓòÉ

o The DECIPHS utility program requires that a DOS session be started from the
  Windows environment; this is not supported.

o To run in a WIN-OS/2 window, change the object's settings to minimize to the
  desktop.

o The directory created by Arts & Letters is named A&L.  The "&" character is a
  reserved character of the command shell, CMD.EXE; it is used for conjugated
  command lines.  To change to the A&L directory with the CD command you must
  use one of two methods of quoting the directory name.

  The first method is to prefix the "&" in A&L with a ^ (caret, shift 6):

   CD A^&L

  The second method is to surround the entire directory name with quotation
  marks ("):

   CD "A&L"

o If you are running Arts & Letters and you get a system error (a GDI trap),
  you must restart the operating system before running the program again. This
  is because the program left a portion of itself running when it ended and
  will not start a new copy of itself while that portion is running.  This also
  means that when you restart the computer, Arts & Letters will start again
  automatically.  It is recommended that you close the copy that is launched on
  system startup and start the program from its icon when you intend to run it
  in a window.


ΓòÉΓòÉΓòÉ 5.7. AutoCAD Version 10 (DOS) ΓòÉΓòÉΓòÉ

o Close the program from the desktop.


ΓòÉΓòÉΓòÉ 5.8. AutoCAD (OS/2) ΓòÉΓòÉΓòÉ

o Some of the background colors are set to an unusually pale color that does
  not show up well on XGA monitors.


ΓòÉΓòÉΓòÉ 5.9. AutoManager 4.0 (DOS) ΓòÉΓòÉΓòÉ

o The version of the program that uses extended memory uses an unsupported DOS
  memory extender.  Use the real-mode version.

o The program expects COMMAND.COM to be in the root directory of drive C:\.
  Copy COMMAND.COM from the C:\OS2\MDOS directory to C:\.


ΓòÉΓòÉΓòÉ 5.10. Borland C++ 2.0 (DOS) ΓòÉΓòÉΓòÉ

o Set the DPMI_DOS_API DOS setting to ENABLED.


ΓòÉΓòÉΓòÉ 5.11. Central Point Backup for DOS 7.1 (DOS) ΓòÉΓòÉΓòÉ

o Displays meaningless characters when running in a DOS window session.  Run
  this program only in a DOS full-screen session.


ΓòÉΓòÉΓòÉ 5.12. Central Point PC Tools Deluxe 7.1 (Windows) ΓòÉΓòÉΓòÉ

o Many of the utility programs require starting a DOS session from Windows;
  this is not supported.  Start these programs from a separate DOS session.

o The backup feature of this program performs in a manner similar to Central
  Point Backup for Windows, which is in the list of programs that perform
  restricted activities.  If you experience difficulty backing up on a
  diskette, back up on an alternate device, such as a network drive or a tape
  drive.


ΓòÉΓòÉΓòÉ 5.13. Commander Keen (DOS) ΓòÉΓòÉΓòÉ

o Set the VIDEO_RETRACE_EMULATION DOS setting to OFF.


ΓòÉΓòÉΓòÉ 5.14. Control Room 1.0 (DOS) ΓòÉΓòÉΓòÉ

o You must run this program in a DOS full-screen session for the screen
  blanking feature to work correctly.


ΓòÉΓòÉΓòÉ 5.15. CorelDRAW 2.0 (OS/2) ΓòÉΓòÉΓòÉ

o If you do a large amount of printing while in this program, it is possible
  that you might run out of system resources.  To avoid this, you should
  periodically save your work and exit CorelDRAW, then restart the program and
  continue your work.


ΓòÉΓòÉΓòÉ 5.16. CorelDRAW 2.0 (Windows) ΓòÉΓòÉΓòÉ

o Install the program in a DOS session.

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.17. CorelDRAW 2.1 (Windows) ΓòÉΓòÉΓòÉ

o To install this program:

    1. Start a DOS session.

    2. Run FFIX /date (Note that "date" must be lowercase).

    3. Run WINOS2 (from the command line).

    4. Install the program.

    5. Exit WIN-OS/2.

    6. Run FFIX /u.

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.18. dBase IV 1.1 (DOS) ΓòÉΓòÉΓòÉ

o Set the DOS_FILES DOS setting to 30.  Add DBASE.EXE,5,0,255 to the
  DOS_VERSION DOS setting.  With Hyperdisk, add DBASE1.EXE,5,0,255 to the
  DOS_VERSION DOS setting.

o When using Hyperdisk, you might have to adjust the EMS and XMS memory limits.

o With the multi-user version, the program must be run in a Specific-DOS
  session.


ΓòÉΓòÉΓòÉ 5.19. Designer (OS/2) ΓòÉΓòÉΓòÉ

o The MIRRORS.DLL that comes with this program must be installed in the program
  directory, as opposed to the C:\OS2\DLL directory, and the program must be
  started from this directory.  This is because OS/2 2.0 comes with its own
  dynamic link library named MIRRORS.DLL.


ΓòÉΓòÉΓòÉ 5.20. Drafix CAD Version 1.11 (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.21. Drafix CAD Version 3.0 (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.22. Dynacomm Asynchronous OS/2 (OS/2) ΓòÉΓòÉΓòÉ

o The DLL's included with this product must not be in the same directory as the
  executable file.  Put them in a separate directory and add that directory to
  the end of the LIBPATH in the CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 5.23. Enhanced Editor (OS/2) ΓòÉΓòÉΓòÉ

o The OS/2 Enhanced Editor supports up to 99 fonts.  If additional fonts are
  installed, unpredictable results might occur.


ΓòÉΓòÉΓòÉ 5.24. F19 (DOS) ΓòÉΓòÉΓòÉ

o Set the HW_ROM_TO_RAM DOS setting to ON and the VIDEO_RETRACE_EMULATION DOS
  setting to OFF.


ΓòÉΓòÉΓòÉ 5.25. F-117A Stealth Fighter 2.0 (DOS) ΓòÉΓòÉΓòÉ

o Set the VIDEO_RETRACE_EMULATION DOS setting to OFF.

o If the program appears to stop at a blank screen soon after you start it,
  press Esc and the program will continue.  Once you are past the opening
  screens, the program runs correctly.


ΓòÉΓòÉΓòÉ 5.26. Fastback Plus 2.1 and 3.04 (DOS) ΓòÉΓòÉΓòÉ

o If you experience difficulty backing up on a diskette, back up on an
  alternate device, such as a network drive or a tape drive.


ΓòÉΓòÉΓòÉ 5.27. FastLynx 1.1 (DOS) ΓòÉΓòÉΓòÉ

o To use the serial port with this program, remove the
  DEVICE=C:\OS2\MDOS\VCOM.SYS statement from CONFIG.SYS.  Using the parallel
  port works correctly.

o Due to its high speed, the program sometimes fails.  If this occurs, simply
  end the program; system integrity is not compromised.  To minimize the
  possibility of this error condition, set the following DOS settings:

   HW_TIMER = ON
   IDLE_SENSITIVITY = 100
   IDLE_SECONDS = 10


ΓòÉΓòÉΓòÉ 5.28. FormBase 1.2 (Windows) ΓòÉΓòÉΓòÉ

o The SHARE statement is automatically added to AUTOEXEC.BAT during program
  installation.  Use an editor to remove the SHARE command from AUTOEXEC.BAT.

o When running this program and Lotus 123 in the same Windows session, this
  program must be started first.


ΓòÉΓòÉΓòÉ 5.29. Form Publisher (Windows) ΓòÉΓòÉΓòÉ

o Ensure that the program's printer driver is installed before running the
  program.


ΓòÉΓòÉΓòÉ 5.30. FotoMan (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.31. Framework III 1.1 (DOS) ΓòÉΓòÉΓòÉ

o The program expects COMMAND.COM to be in the root directory of C:\.  Copy
  COMMAND.COM from the C:\OS2\MDOS directory to C:\.

o Disable the program's print spooler; using it might cause an error.


ΓòÉΓòÉΓòÉ 5.32. Harvard Graphics (Windows) ΓòÉΓòÉΓòÉ

o When installing this program under WIN-OS/2, you will receive an error dialog
  box.  Select OK in the dialog box and installation will complete
  successfully.

o When running in a window, the Color Selection windows are missing the Color
  Selection grid.  Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.33. Harvard Draw (Windows) ΓòÉΓòÉΓòÉ

o When installing this program under WIN-OS/2, you will receive an error dialog
  box.  Select OK in the dialog box and installation will complete
  successfully.


ΓòÉΓòÉΓòÉ 5.34. hDC FileApps 1.0 (Windows) ΓòÉΓòÉΓòÉ

o Uses the Windows Notepad for a README text file during installation.
  Indicate that you do not wish to read the file and installation will
  continue.


ΓòÉΓòÉΓòÉ 5.35. HP New Wave 3.0 (Windows) ΓòÉΓòÉΓòÉ

o Install the program under DOS.  If you experience problems with program or
  session termination, set UseOS2shield=0 in SYSTEM.INI (in the
  \OS2\MDOS\WINOS2 directory on your start-up drive).  If that does not help,
  run the program in a full screen WIN-OS/2 session.


ΓòÉΓòÉΓòÉ 5.36. IBM 3363 Optical Disk Drive* ΓòÉΓòÉΓòÉ

o The software for this product must be run in a Specific-DOS session that is
  started from your A: drive.

o You should run only a small number of other processes, when using this
  product.


ΓòÉΓòÉΓòÉ 5.37. IBM PC/3270 V2.0* (DOS) ΓòÉΓòÉΓòÉ

o First, the program must be migrated using the OS/2 Migration utility program.
  Then, set the VIDEO_MODE_RESTRICTION DOS setting to CGA and add
  "D:\[path]DXMA0MOD.SYS" and "D:\[path]DXMC0MOD.SYS" to the DOS_DEVICE DOS
  setting.


ΓòÉΓòÉΓòÉ 5.38. IBM PC/3270 V2.0* (Windows) ΓòÉΓòÉΓòÉ

o First, the program must be migrated using the OS/2 Migration utility program.
  Then add " /C PC3270WO.BAT" to the DOS_SHELL WIN-OS/2 setting and add
  "D:\[path]DXMA0MOD.SYS", "D:\[path]DXMC0MOD.SYS", and "D:\[path]PCS802.SYS
  V=N" to the DOS_DEVICE WIN-OS/2 setting.  Then on the WIN-OS/2 Session
  settings page, set the "Separate session" setting to ON (by clicking on the
  box until a check-mark appears).


ΓòÉΓòÉΓòÉ 5.39. Intel SatisFAXtion ΓòÉΓòÉΓòÉ

o The installation program displays the message "You have inserted the wrong
  diskette" when changing from disk one to disk two.  After the error message
  is displayed, press Enter and the program will continue with installation.

o At the end of installation of the Intel SatisFAXtion you are told to remove
  the diskette and press any key to reboot your machine.  Instead, shut down
  the operating system and restart your computer.

o If SatisFAXtion software is loaded into each DOS session, it might cause the
  fax to stop if another DOS session is started.  Set up one DOS session to be
  used for faxing, and load the device driver and executable files only into
  that DOS session.  To do this, take the following steps:

    1. Edit AUTOEXEC.BAT.

    2. Cut the last two lines referring to the Intel SatisFAXtion board to the
       clipboard and save the file (using DOS Command File for the file type).

    3. Open a New file.

    4. Paste the last two lines into the new file.

    5. Save the new file as FAX.BAT, using DOS Command File as the file type.

    6. Edit CONFIG.SYS and cut the last two lines relating to the Intel
       SatisFAXtion board to the clipboard (cut only the last line if you do
       not have a scanner installed).

    7. Save the file using Plain Text as the file type.

    8. In the Command Prompts folder, select a DOS Full Screen icon, press the
       Ctrl key and mouse button two at the same time, move the mouse pointer
       to an empty area in the folder, and release the mouse button and the
       Ctrl key. This creates a copy of DOS Full Screen.

    9. Put the mouse pointer over your new icon and press button two.

   10. Click on the arrow next to Open, and select Settings.

   11. Go to the Session page and select the DOS settings push button.

   12. Go to DOS_DEVICE and press mouse button one.  Move the mouse to the
       dialog area and press button one (there should be a blinking cursor
       now).

   13. Paste the text that you cut from the CONFIG.SYS file and select Save.

   14. Go to the General page and replace the contents of the Title box with
       FAX (or whatever other title you choose).

   15. If you want to edit the new session's icon, go to the General page and
       select the Edit push button.

   16. If you want to have this session start each time your system starts,
       move the icon to the Start Up folder.

   17. Whenever you start this session, type FAX to run the FAX.BAT file before
       using the SatisFAXtion board.

  Use the fax board in only one session at a time.

o If you install using this procedure and you receive error messages, install
  the program under DOS.


ΓòÉΓòÉΓòÉ 5.40. King's Quest (DOS) ΓòÉΓòÉΓòÉ

o Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or set the
  DOS_HIGH DOS setting to OFF.


ΓòÉΓòÉΓòÉ 5.41. LAN Support Program Device Drivers (DOS) ΓòÉΓòÉΓòÉ

o If you opened a DOS session with the DOS LAN Support Program (LSP) device
  drivers, and subsequently closed the session, you must ensure that the
  Token-Ring Adapter is reset before using the LAN from another DOS session.
  To ensure that the Token-Ring Adapter is reset, use RESETOKN.EXE or
  RESETOKN.SYS.  These files can be retrieved from CompuServe by issuing GO
  IBMOS2 and downloading RESTKN.ZIP from SECTION 17, IBMFILES, or they can be
  retrieved from the IBM National Support Center Bulletin Board System by
  downloading RESTKN.ZIP.

o The IBM Token-Ring Adapter should be used by only one session at a time.


ΓòÉΓòÉΓòÉ 5.42. LANtastic 4.1 (DOS) ΓòÉΓòÉΓòÉ

o Run this program in a Specific-DOS session.  Set DOS_STARTUP_DRIVE DOS
  setting to the location of a DOS kernel to boot from.

o If you are using Artisoft AE-2 or AE-3 adapter cards, set your cards to 8-bit
  mode, as described in the adapter documentation.


ΓòÉΓòÉΓòÉ 5.43. LapLink III 3.0 (DOS) ΓòÉΓòÉΓòÉ

o We recommend using the parallel port.  To use the serial port with this
  program, comment out the VCOM.SYS and COM.SYS statements from CONFIG.SYS (by
  putting "REM " at the beginning of the line) and restart the computer.  To
  use the serial port for other purposes, uncomment the lines in CONFIG.SYS and
  restart the computer.


ΓòÉΓòÉΓòÉ 5.44. Linkway Mammals (DOS) ΓòÉΓòÉΓòÉ

o Photomotion programs might exhibit some audio breakup and video hesitation
  during periods of CD ROM access.


ΓòÉΓòÉΓòÉ 5.45. Linkway Presidents (DOS) ΓòÉΓòÉΓòÉ

o Photomotion programs might exhibit some audio breakup and video hesitation
  during periods of CD ROM access.


ΓòÉΓòÉΓòÉ 5.46. Lotus 123 for Windows 1.0 (Windows) ΓòÉΓòÉΓòÉ

o Set the DPMI_MEMORY_LIMIT DOS setting to a minimum of 3MB.

o After migrating the program to the workplace shell, copy the file 123W.INI to
  the \OS2\MDOS\WINOS2 directory (from the directory previously containing
  Windows 3.0).


ΓòÉΓòÉΓòÉ 5.47. Lotus Freelance Graphics for OS/2 (OS/2) ΓòÉΓòÉΓòÉ

o If you experience installation problems, contact the Lotus Development
  Corporation. Lotus will provide a fix.

o If you experience problems with the color, change the palette from the
  Freelance menus.  Instructions on how to do this can be found in the Lotus
  Freelance Graphics for OS/2 User's Guide.  A set of new default palettes for
  Freelance Graphics is available.  These can be retrieved from CompuServe by
  issuing GO IBMOS2 and downloading PALETT.ZIP from SECTION 17, IBMFILES, or
  they can be retrieved from the IBM National Support Center Bulletin Board
  System by downloading PALETT.ZIP.


ΓòÉΓòÉΓòÉ 5.48. Lotus Freelance Graphics for Windows (Windows) ΓòÉΓòÉΓòÉ

o The pointer to printer objects points to Screen Show instead of to the
  printer.


ΓòÉΓòÉΓòÉ 5.49. Lotus Magellan 2.0 (DOS) ΓòÉΓòÉΓòÉ

o The UNDELETE function in the program uses physical sector addressing, which
  is not supported.  Use the OS/2 UNDELETE command.


ΓòÉΓòÉΓòÉ 5.50. Lotus Notes (OS/2) ΓòÉΓòÉΓòÉ

o To use Notes 2.x, you must delete the file QNC.EXE from the Notes program
  directory. This file is used only for support in the field, and, therefore,
  its removal will not affect program execution.


ΓòÉΓòÉΓòÉ 5.51. MagiCorp (Windows) ΓòÉΓòÉΓòÉ

o Running this program with other programs in the same WIN-OS/2 session might
  cause a system halt.  Run this program by itself in a WIN-OS/2 full-screen
  session.


ΓòÉΓòÉΓòÉ 5.52. Mathcad 3.0 (Windows) ΓòÉΓòÉΓòÉ

o To install this program:

    1. Start a DOS session.

    2. Run FFIX /date (Note that "date" must be lowercase).

    3. Install the program (the installation program is a DOS program).

    4. Run FFIX /u.


ΓòÉΓòÉΓòÉ 5.53. MicroProse Civilization (DOS) ΓòÉΓòÉΓòÉ

o Set the VIDEO_RETRACE_EMUL DOS setting to OFF and the HW_TIMER DOS setting to
  ON.


ΓòÉΓòÉΓòÉ 5.54. Microsoft Bookshelf - CD-ROM Reference Library** (DOS/Multimedia) ΓòÉΓòÉΓòÉ

o Requires version 6.14 of the mouse device driver, MOUSE.COM, which comes with
  the product.

o Animation programs might exhibit some audio breakup and video hesitation
  during periods of CD ROM access.


ΓòÉΓòÉΓòÉ 5.55. Microsoft Chart 3.0** (DOS) ΓòÉΓòÉΓòÉ

o Install the program's mouse driver, and set the MOUSE_EXCLUSIVE_ACCESS DOS
  setting to ON.


ΓòÉΓòÉΓòÉ 5.56. Microsoft Codeview** (DOS/OS/2) ΓòÉΓòÉΓòÉ

o When using the protect mode version, CVP 2.2 (for OS/2), trace through the
  source code, rather than through the assembler language.

o In order for the program to work correctly, delete the PWBHLP.PXT help file.


ΓòÉΓòÉΓòÉ 5.57. Microsoft Codeview for Windows Version 3.0** (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.58. Microsoft Excel for DOS 2.1** (DOS) ΓòÉΓòÉΓòÉ

o Set the XMS_MEMORY_LIMIT DOS setting to 0.


ΓòÉΓòÉΓòÉ 5.59. Microsoft Excel for OS/2 3.0** (OS/2) ΓòÉΓòÉΓòÉ

o The Help index and the Keyboard Help windows operate incorrectly.  Avoid
  using these functions.


ΓòÉΓòÉΓòÉ 5.60. Microsoft Excel for Windows 3.0** (Windows) ΓòÉΓòÉΓòÉ

o Deselect the public setting to use the clipboard.

o When using dynamic data exchange (DDE), run in the same WIN-OS/2 session as
  the Windows program it is communicating with.


ΓòÉΓòÉΓòÉ 5.61. Microsoft Money 1.0** (Windows) ΓòÉΓòÉΓòÉ

o Calls the Windows Calculator accessory program.  Use the OS/2 Calculator
  mini-application program in the Productivity folder.


ΓòÉΓòÉΓòÉ 5.62. Microsoft QuickC** (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.63. Microsoft Project for Windows 1.0** (Windows) ΓòÉΓòÉΓòÉ

o Must be installed in a DOS session.


ΓòÉΓòÉΓòÉ 5.64. Microsoft Windows 3.0** (DOS) ΓòÉΓòÉΓòÉ

o We recommend that you run Windows programs under WIN-OS/2, which supports
  both Standard and Real mode Windows programs.  If, however, you choose to run
  this program, run it in Real mode only.


ΓòÉΓòÉΓòÉ 5.65. More Windows (Windows) ΓòÉΓòÉΓòÉ

o If you use the Full-Page Paper White mode or Full Screen Color mode the
  screen might be disrupted.  Avoid using these modes.


ΓòÉΓòÉΓòÉ 5.66. National Geographics Mammals (DOS) ΓòÉΓòÉΓòÉ

o Photomotion programs might exhibit some audio breakup and video hesitation
  during periods of CD ROM access.


ΓòÉΓòÉΓòÉ 5.67. The Norton Backup 1.2 (DOS) ΓòÉΓòÉΓòÉ

o You might experience diminished performance when backing up to diskette.


ΓòÉΓòÉΓòÉ 5.68. The Norton Desktop (Windows) ΓòÉΓòÉΓòÉ

o This program assumes that, if it is not the first program loaded, another
  desktop is running.  Include the UseOS2shield=0 statement in SYSTEM.INI (in
  the \OS2\MDOS\WINOS2 directory on your start-up drive).

o If you experience difficulty formatting a diskette, use the OS/2 FORMAT
  FORMAT command.  If you experience difficulty backing up on a diskette, back
  up on an alternate device, such as a network drive or a tape drive.

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.69. The Norton Utilities 5.0 (DOS) ΓòÉΓòÉΓòÉ

o The UNDELETE functions require physical sector addressing, which is not
  supported.  Use the OS/2 UNDELETE UNDELETE command.

o The utility programs that manipulate the hard disk (for example, UNDELETE,
  UNFORMAT, DISKTOOL, CALIBRATE, the Disk Doctor, and the Disk Editor) can
  cause a system halt.  Some of these programs can be used on floppy diskettes.


ΓòÉΓòÉΓòÉ 5.70. PaintShow Plus 2.21 (DOS) ΓòÉΓòÉΓòÉ

o Load the version of MOUSE.COM that comes with the program, before starting
  the program.


ΓòÉΓòÉΓòÉ 5.71. Paradox 3.5 (DOS) ΓòÉΓòÉΓòÉ

o The version of the program that uses extended memory uses an unsupported DOS
  memory extender.  Use the standard version of the program.


ΓòÉΓòÉΓòÉ 5.72. Peachtree Complete III 5.0 (DOS) ΓòÉΓòÉΓòÉ

o Set the DOS_FILES DOS setting to 60.

o The program's Lookup function does not list all the companies that have been
  entered into the program's list of companies; it displays meaningless
  characters.


ΓòÉΓòÉΓòÉ 5.73. Perform Pro 1.0 (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.74. PFS: First Choice (DOS) ΓòÉΓòÉΓòÉ

o When the program is run in a DOS window the mouse pointer does not reflect
  tool selection.

o Set the baud rate to 2400 or lower when using the communication feature.


ΓòÉΓòÉΓòÉ 5.75. PFS: WindowWorks 1.75 (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.76. Photostyler (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.


ΓòÉΓòÉΓòÉ 5.77. Publisher's PowerPak  2.1 (Windows) ΓòÉΓòÉΓòÉ

o Create the directory

    C:\OS2\MDOS\WINOS2\POWERPAK,

  before running the installation batch file.


ΓòÉΓòÉΓòÉ 5.78. Quattro Pro 3.0 (DOS) ΓòÉΓòÉΓòÉ

o Install printers from within the program, rather than during program
  installation.


ΓòÉΓòÉΓòÉ 5.79. Quicken (DOS) ΓòÉΓòÉΓòÉ

o Remove the DOS=HIGH statement, if one exists, from CONFIG.SYS or set the
  DOS_HIGH DOS setting to OFF.


ΓòÉΓòÉΓòÉ 5.80. Quicken for Windows (Windows) ΓòÉΓòÉΓòÉ

o Calls the Windows Calculator accessory program.  Use the Calculator
  mini-application program in the Productivity folder.


ΓòÉΓòÉΓòÉ 5.81. Risk (DOS) ΓòÉΓòÉΓòÉ

o Do not use the program's shutdown function.


ΓòÉΓòÉΓòÉ 5.82. SantaFe Media Manager (DOS) ΓòÉΓòÉΓòÉ

o To install this program:

    1. Start a DOS session.

    2. Run FFIX /find (Note that "find" must be lowercase).

    3. Install the program.

    4. Run FFIX /u.


ΓòÉΓòÉΓòÉ 5.83. SideKick (OS/2) ΓòÉΓòÉΓòÉ

o A printer must be installed and present on the desktop to use the Notepad.


ΓòÉΓòÉΓòÉ 5.84. Signmaster 5.11 (DOS) ΓòÉΓòÉΓòÉ

o The plot/preview feature causes an illegal instruction to be issued.


ΓòÉΓòÉΓòÉ 5.85. Soft Term (OS/2) ΓòÉΓòÉΓòÉ

o In the Send File and Receive File windows, the first time the drive is
  changed the Directory window updates incompletely.  After the first time, the
  Directory window works normally.


ΓòÉΓòÉΓòÉ 5.86. SoundBlaster (DOS) ΓòÉΓòÉΓòÉ

o The SBTEST utility program reports an incorrect DMA level during
  installation.  Disregard the error message and continue with installation.
  The program will be installed correctly.

o The PARROT program does not run in a DOS session.


ΓòÉΓòÉΓòÉ 5.87. Space Quest IV (DOS) ΓòÉΓòÉΓòÉ

o Set the DOS_BACKGROUND_EXECUTION DOS Setting to OFF so that the program is
  suspended when it is placed in the background.

o Set up the program so that it does not use extended memory.

o For best performance, run this program in a DOS full-screen session.

o For computers with a SoundBlaster card, change to the drive and directory
  which contains Space Quest IV and enter

    SQ4FIX

  on the command line.


ΓòÉΓòÉΓòÉ 5.88. SQLWindows 3.0 (Windows) ΓòÉΓòÉΓòÉ

o The program accesses drive A: at intermittent intervals.  Keeping a scratch
  diskette or an empty diskette in drive A: will save you from having to
  respond to "The A: device is not ready" error windows.


ΓòÉΓòÉΓòÉ 5.89. Turbo C++ 2.0 (DOS) ΓòÉΓòÉΓòÉ

o The version of the program that uses extended memory uses an unsupported DOS
  memory extender.  Use the standard version of the program.


ΓòÉΓòÉΓòÉ 5.90. Turbo Debugger 2.01 (DOS) ΓòÉΓòÉΓòÉ

o The version of the program that uses extended memory uses an unsupported DOS
  memory extender.  Use the standard version of the program.

o TD386, the 386 version of Turbo Debugger, manipulates the 80386 control
  registers; this is not supported.


ΓòÉΓòÉΓòÉ 5.91. Turbo Debugger for Windows (Windows) ΓòÉΓòÉΓòÉ

o Run the program in a WIN-OS/2 full-screen session.

o The screen is temporarily corrupted when this program is called from Turbo
  C++.  The screen is restored on the first repaint (a repaint can be forced by
  clicking the mouse on several different windows).


ΓòÉΓòÉΓòÉ 5.92. Turbo Pascal 6.0 (DOS) ΓòÉΓòÉΓòÉ

o The version of the program that uses extended memory uses an unsupported DOS
  memory extender.  Use the standard version of the program.


ΓòÉΓòÉΓòÉ 5.93. The Way You Work (DOS/Windows) ΓòÉΓòÉΓòÉ

o Install this program under DOS.  Once installed, the program can be run in a
  DOS or WIN-OS/2 session.


ΓòÉΓòÉΓòÉ 5.94. Windows Multimedia Extensions (Windows) ΓòÉΓòÉΓòÉ

o If you are running this program and another program that uses the audio
  adapter at the same time, unpredictable results might occur.

o The OS/2 Multimedia Presentation Manager avoids this problem.


ΓòÉΓòÉΓòÉ 5.95. WINFAX PRO (Windows) ΓòÉΓòÉΓòÉ

o Run this program only in a WIN-OS/2 full-screen session.

o If you are using Dynamic Data Exchange (DDE), avoid switching away from the
  WIN-OS/2 full-screen session in which you are running; switching from the
  WIN-OS/2 session to another session might break the DDE link.


ΓòÉΓòÉΓòÉ 5.96. Wing Commander II (DOS) ΓòÉΓòÉΓòÉ

o If you are running on a slower computer, turn the sound option off.


ΓòÉΓòÉΓòÉ 5.97. WordPerfect for Windows (Windows) ΓòÉΓòÉΓòÉ

o Change to the directory that contains WPWINFIL.EXE and run:

    FIXWP WPWINFIL.EXE.

  (To enable WordPerfect for Windows to run under DOS and Windows 3.0 again,
  run UNFIXWP in a similar manner.)


ΓòÉΓòÉΓòÉ 5.98. WordPerfect Office 3.0 (DOS) ΓòÉΓòÉΓòÉ

o Install the keyboard-enhancement utility program manually after program
  installation, by adding it to CONFIG.SYS.


ΓòÉΓòÉΓòÉ 5.99. Xtree Pro Gold 2.0 (DOS) ΓòÉΓòÉΓòÉ

o The Zip Manager feature cannot find the zip file it is to act upon.  Avoid
  using this feature.


ΓòÉΓòÉΓòÉ 6. Performance ΓòÉΓòÉΓòÉ

Following are some performance considerations that you should be aware of.  For
more performance guidelines, see the "Information and Planning Guide" document
that can be obtained through your point of purchase or retrieved through
CompuServe.

The minimum memory requirement for OS/2 2.0 is 4MB.  (This includes up to 128KB
that is used on some machines for ROM to RAM remapping).

Some systems use more than 128KB for other purposes, so less than the minimum
required memory is available.  On these systems, you might need another 512KB
to 1MB to satisfy the minimum requirements.  Check your system to see if it
offers a way to return the memory so that you can return to the minimum
requirement.

Users concerned with response times when using some system functions, such as
loading programs, starting sessions, and switching between sessions, can
improve performance by increasing system memory.  If you are running on a
constrained system (small hard disk, 16-MHz or less processor, 4MB of memory),
an additional 2MB of memory will improve performance.  In the entry memory
system (4MB), the recommended file system is the FAT file system.

Related Information:

o Swapper File
o File Systems
o DOS Applications
o Windows Applications
o Application Usage
o Freeing Memory
o Reducing Hard Disk Space


ΓòÉΓòÉΓòÉ 6.1. Swapper File ΓòÉΓòÉΓòÉ

The system automatically pre-allocates the SWAPPER.DAT file based on the size
of installed memory.  This is done to optimize performance and reduce disk
fragmentation.  To tune the size of the swapper file, see the information about
SWAPPATH in the "Command Reference."


ΓòÉΓòÉΓòÉ 6.2. File Systems ΓòÉΓòÉΓòÉ

Many performance changes have been incorporated into OS/2 2.0 File Systems.
Both file systems read ahead (for sequential I/O), lazy write to disk, and
accept threshold parameters.

A disk cache size is preselected by the system based on installed memory, disk
size, and file systems installed. The default for the entry memory system (4MB)
is a cache size of 128KB.  To tune the size of the disk cache, see the
information about DISKCACHE in the "Command Reference."


ΓòÉΓòÉΓòÉ 6.3. DOS Applications ΓòÉΓòÉΓòÉ

You can improve the performance of some DOS applications by adjusting the DOS
settings.  If the application does not require extended or expanded memory,
these values can be set to zero.  This will provide maximum performance.

Some DOS applications use polling techniques to poll the system for work. An
example is an application that appears to be idle at an input prompt, but is in
fact polling the keyboard looking for keystrokes.  Use the IDLE_SENSITIVITY DOS
setting to detect this occurrence and put the application to sleep when it is
polling.


ΓòÉΓòÉΓòÉ 6.4. Windows Applications ΓòÉΓòÉΓòÉ

Windows applications are generally started in one WIN-OS/2 session, unless
specifically set to run in their own WIN-OS/2 session.  If you use several
applications simultaneously, you might want to increase the DPMI memory limit
before starting the first application.  The first application started
determines the DPMI memory available for all subsequent Windows applications
that are used.

In low memory configurations, you can run multiple Windows applications in one
WIN-OS/2 session. This reduces both memory and swapper-file requirements.

With a WIN-OS/2 window session, a new session is created every time you
double-click on an active object.  To restore the currently active object:

o Double-click on the minimized application object, or

o Display the OS/2 Window List and double-click on the application name.

If you choose to migrate your Windows applications (at installation time or
later using MIGRATE), most Windows applications will execute in one WIN-OS/2
session.  If you set up a Windows application and do not use MIGRATE, each
program executes in its own WIN-OS/2 session.

If you are running Windows applications in a single WIN-OS/2 session, the
Windows clipboard can be changed from PUBLIC to PRIVATE for increased
performance.  Setting it to PRIVATE means that it can be used in the single
Windows environment only.

When a large volume of data is being sent to the clipboard in a WIN-OS/2 Window
session, you might receive the message:

Data not saved, possible memory or disk space error
This data not available in clipboard

followed by the message:

Do you want to exit clipboard?

Selecting OK to the second message will make the clipboard private to that
WIN-OS/2 session.  Data that was previously sent to the public clipboard might
have remained private.  You might want to use the private clipboard for
applications seeing these mes sages.

When you exit from a WIN-OS/2 session, the system leaves the clipboard and DDE
loaded.  If you will not be returning to a WIN-OS/2 session, close both the
clipboard and DDE.  Use the PM Window List to see if they are active.

To permanently disable public DDE and clipboard interchange between Windows
applications and PM applications, and between Windows applications in separate
WIN-OS/2 sessions, edit the \OS2\MDOS\WINOS2\SYSTEM.INI file.  In the [boot]
section you will find the names of these two programs in the SAVDMApps= line,
the MAVDMApps= line, and the WOS2VDMApps= line.  By removing the names of the
programs from these lines, the programs will not be automatically started.
Adding them back will cause them to be started the next time a WIN-OS/2 session
starts up.


ΓòÉΓòÉΓòÉ 6.5. Applications Usage ΓòÉΓòÉΓòÉ

If you have an application that you always use, you can set up the application
in the Startup folder to load when the system is started.

To avoid reloading frequently used applications, minimize the application after
use and simply maximize it to use it again. You can find the application in the
window manager.

If you use several different applications, the icons (objects) can be placed on
the desktop or in a folder.  The folder can be set to open when the system is
restarted.


ΓòÉΓòÉΓòÉ 6.6. Freeing Memory ΓòÉΓòÉΓòÉ

Close opened applications when you are not going to use them again.

Close folders that you do not need.  Also move commonly used functions out of
folders and onto your desktop, and close the folders that contained the icons.


ΓòÉΓòÉΓòÉ 6.7. Reducing Hard Disk Space ΓòÉΓòÉΓòÉ

To save hard disk space, be certain to install only the functions you need.  If
you have installed the productivity aids and the games, and later only want a
subset of these, delete all \OS2\APP and \OS2\APP\DLL files and use INSTALL to
selectively install the items you want.  Additionally, delete TUTORIAL.HLP in
\OS2\HELP\TUTORIAL if you no longer need the tutorial.


ΓòÉΓòÉΓòÉ 7. Windows Version 3.0 Programs Support ΓòÉΓòÉΓòÉ

o If you are running WIN-OS/2 window sessions, you cannot have any statement in
  the AUTOEXEC.BAT file that prompts the user for input.

o If you are running a WIN-OS/2 full-screen session and you have an 8514
  display, set the VIDEO_8514A_XGA_IOTRAP DOS setting to OFF and set the
  VIDEO_SWITCH_NOTIFICATION DOS setting to ON.

o Current information for WIN-OS/2* window sessions in high-resolution video
  modes will be available from CompuServe, the IBM National Support Center
  Bulletin Board System, the OS/2 Bulletin Board System, and IBMLINK.

o Do not use the SETUP.EXE shipped with Windows 3.0.  Instead, use the
  SETUP.EXE shipped with WIN-OS/2 to ensure your environment will be properly
  maintained for use in OS/2 2.0.  Use the Selective Install choice (in OS/2
  2.0) to change video drivers for VGA, 8514, XGA*, EGA, and CGA, and for mouse
  drivers.

o If you are running a WIN-OS/2 full-screen session with an XGA video device
  driver and your Windows icons are not clear, use the Control Panel to choose
  another color scheme for the WIN-OS/2 desktop.

o Do not change mouse buttons from the WIN-OS/2 Control Panel if you are using
  WIN-OS/2 window sessions.  Change mouse buttons from the Workplace Shell to
  change the WIN-OS/2 mouse buttons in the WIN-OS/2 environment. The WIN-OS/2
  Control Panel can still be used for changing mouse buttons in WIN-OS/2
  full-screen sessions.

o If the VIDEO_SWITCH_NOTIFICATION DOS setting is ON, wait until you see your
  WIN-OS/2 desktop in a full-screen session before switching back to the
  Workplace Shell desktop.  If the session does not start successfully, close
  it then restart it.

o The value for the VIDEO_SWITCH_NOTIFICATION DOS setting should not be changed
  for an active WIN-OS/2 session.

o Clipboard and DDE default to PRIVATE in real-mode WIN-OS/2 sessions.

o If you install the USA (English) version of OS/2 2.0, and you want to change
  the system configuration to another country or language, run Selective
  Install to make the changes effective for PM.  To make the changes effective
  for WIN-OS/2, start WIN-OS/2 in full-screen mode, open the Control Panel, and
  use the international option to make your changes.

o The EXPAND.EXE utility program for WIN-OS/2 is located on OS/2 2.0 diskette
  9.  This program is required to expand Windows device drivers supplied by
  equipment manufacturers.

Related Information:

o Printing from WIN-OS/2


ΓòÉΓòÉΓòÉ 7.1. Printing from WIN-OS/2 ΓòÉΓòÉΓòÉ

If your printer is connected to LPTx or LPTx.OS2, be sure that the OS/2 spooler
is active and the Windows spooler is disabled.  When the OS/2 spooler is
active, Windows applications print jobs from Windows applications spool
directly to the OS/2 spooler.  Therefore, multiple print jobs can be spooled
asynchronously from the same WIN-OS/2 session or multiple WIN-OS/2 sessions.
This does not apply for printing to COMx devices, as there is no spooling for
COM devices.


ΓòÉΓòÉΓòÉ 8. Video/Graphic Support ΓòÉΓòÉΓòÉ

OS/2 2.0 fully supports EGA and VGA.  Because of the highly graphical user
interface provided by the Workplace Shell, use of OS/2 2.0 in CGA mode will be
difficult and is not recommended.  Applications designed for CGA mode are
supported and can be run even when OS/2 2.0 is running in EGA, VGA, or SVGA
mode.  Resolutions above VGA (640x480x16 colors) are referred to as Super VGA
(SVGA).  However, the implementation of SVGA varies widely and requires
different device drivers for different resolutions, as well as different
adapters and systems.  The OS/2 Installation program will correctly configure
Presentation Manager* and WIN-OS/2 drivers for 8514 and XGA.  All SVGA adapters
are supported in VGA mode with the VGA driver provided with OS/2 2.0.

Related Information:

o SVGA
o SVGA ON Utility
o Dual Displays
o Laptop LCD or Monochrome Plasma Displays
o Graphics
o Running VGA PM and WIN-OS/2 Window Sessions in VGA and Windows Full-screen
  Sessions in High Resolution mode


ΓòÉΓòÉΓòÉ 8.1. SVGA ΓòÉΓòÉΓòÉ

The base video system and virtual display device driver in OS/2 2.0 have been
enabled for some of the most popular SVGA chips and boards.  This support is
required to switch between PM and DOS or WIN-OS/2 applications.  Because of the
many implementations and video modes, a limited number of video boards have
been tested.

The following Super VGA boards have been tested and found to work with OS/2 2.0
for DOS applications that make use of SVGA modes:

o Orchid ProDesigner IIs by Orchid Technology (ISA and MCA versions)
o Trident TVGA by Trident Microsystems, Inc. (8900b and c levels)
o STB PowerGraph VGA by STB Systems, Inc.
o Video Seven VRAM II, by Video Seven
o Boca Super VGA by Boca Research Inc.
o VGA Wonder XL Series by ATI Technologies, Inc.

The 8514 Ultra by ATI must be installed as an 8514 and as a primary display; it
will default to high-resolution mode.  Do not install it as VGA.

Please contact the manufacturer of your PC or SVGA video adapter to obtain
device drivers and installation instructions if you want to run Windows or OS/2
applications in SVGA modes.  Information about SVGA support will be available
on CompuServe, the National Support Center Bulletin Board System, the OS/2
Bulletin Board System, as well as many video-board and system manufacturers'
bulletin boards.

We recommend you do NOT run the video-adapter test utility programs in OS/2 2.0
unless the manufacturer has explicitly verified that they run in OS/2 2.0.

Some video adapters require that the computer's DOS BIOS initialize the video
adapter correctly.  If you have one of these adapters, screen text might appear
distorted in an OS/2 full-screen command prompt.  To remedy this, start a DOS
full-screen command prompt, type EXIT, and then switch back to the OS/2
full-screen session; the text should appear normal.

To automate this process, you can create a DOS batch file to run when you start
your computer. Add the following statement to STARTUP.CMD:

START /FS /DOS DOSFS.BAT

Create the file, DOSFS.BAT, and place the following statement in it:

EXIT


ΓòÉΓòÉΓòÉ 8.2. SVGA ON Utility ΓòÉΓòÉΓòÉ

If you have one of the above video adapters and want to run DOS or Windows
applications that make use of SVGA, you must turn on OS/2 2.0 SVGA support.
The OS/2 Installation program detects the type of video chip in the system; it
cannot detect the type of adapter or system board that the video chip has been
implemented on.  You must determine that you have a supported configuration,
and then explicitly enable SVGA.

To enable SVGA, type the following at an OS/2 command prompt or DOS full-screen
command prompt:

SVGA ON

Then restart the system.

When the Installation program detects a supported SVGA video chip (other than
8514 or XGA), it will add the following line to the CONFIG.SYS file:

DEVICE=(OS/2 drive):\OS2\MDOS\VSVGA.SYS

Execution of SVGA ON creates the configuration file, SVGADATA.PMI, in the \OS2
directory.  This file is used by VSVGA.SYS to save and restore the correct
video registers when switching between DOS or Windows programs and Presentation
Manager.  Failure to enable SVGA will cause display errors when switching
between applications that use SVGA.

NOTES:

 1. Over time, more display adapters and PC systems that offer SVGA, will be
    tested. Refer to the bulletin boards mentioned previously, or to the
    manufacturers for the latest support information.

 2. To make use of SVGA modes, you also must install Windows and Presentation
    Manager video display drivers.

 3. If you experience display errors on an SVGA-enabled system, try disabling
    SVGA support by typing SVGA OFF at a command line.  This will delete the
    SVGADATA.PMI file.  Then restart your system.

 4. In some SVGA displays, if you switch to the PM desktop while the screen is
    still drawing, you might experience display errors on the PM desktop.
    Switch back to the SVGA screen, allowing the drawing to complete, and then
    switch back to the PM desktop.


ΓòÉΓòÉΓòÉ 8.3. Dual Displays ΓòÉΓòÉΓòÉ

In multiple XGA configurations, when you switch from DOS to the PM desktop,
your system will not save and restore the hardware registers.

If your machine has an 8514 Ultra adapter and an OS/2 2.0 supported SVGA
adapter, you will need to change the

DEVICE=VVGA.SYS

statement in the CONFIG.SYS file to

DEVICE=VSVGA.SYS


ΓòÉΓòÉΓòÉ 8.4. Laptop LCD or Monochrome Plasma Displays ΓòÉΓòÉΓòÉ

To change the color schemes for OS/2 system windows and create a more readable
display image, change the Scheme Palette as follows:

 1. Use your Reference Diskette or hardware Setup program to set your hardware
    to VGA color, if possible.
 2. Open the System folder.
 3. Select System Setup.
 4. Select Scheme Palette.
 5. Select the right-hand monochrome scheme.

This procedure will optimize the color scheme for gray-scale usage, and also
provide a good set of colors for a VGA desktop presentation.


ΓòÉΓòÉΓòÉ 8.5. Graphics ΓòÉΓòÉΓòÉ

Several fonts have been enhanced in OS/2 2.0.  Some existing applications use
inappropriate font metrics to scale their text.  In some cases, the text
becomes clipped because it no longer fits the available space.


ΓòÉΓòÉΓòÉ 8.6. Running VGA PM and WIN-OS/2 Window Sessions in VGA and Windows Full-screen Sessions in High Resolution mode ΓòÉΓòÉΓòÉ

When running a full-screen WIN-OS/2 session with an 8514 adapter in high
resolution (8514.DRV mode), do not switch away to a different session while an
application is updating the screen or displaying the hourglass.

The following is a procedure for enabling WIN-OS/2 full-screen sessions to run
in high-resolution mode while the Workplace Shell Desktop and WIN-OS/2 window
sessions run in medium-resolution (VGA) mode.  The procedure assumes you are
not familiar with the SYSTEM.INI and WIN.INI files.

Follow the instructions very carefully.  Otherwise, you could cause your
WIN-OS/2 sessions, both window and full-screen, to become inoperable.

 1. Install OS/2 for medium resolution VGA.

    The next step requires you to make backup copies of your SYSTEM.INI and
    WIN.INI files.  DO NOT SKIP THIS STEP.  It is assumed that you have a
    diskette or tape backup copy of your system; instructions follow for a
    backup in the directory only.

 2. Back up the SYSTEM.INI and WIN.INI files.

    Open an OS/2 Window from the Command Prompts folder in the OS/2 System
    folder.  At the [C:\] prompt, type the following and press Enter:

        CD\OS2\MDOS\WINOS2
        COPY WIN.INI WIN.BAK
        COPY SYSTEM.INI SYSTEM.BAK

    Before making changes to the files, be sure the desired high-resolution
    Windows device drivers and fonts are loaded in the system.

 3. Check the \os2\mdos\winos2\system directory for the desired high-resolution
    display device driver.  In this example, the XGA.DRV device driver is used.
    Checking this directory reveals that this device driver is not loaded. (The
    device driver might be loaded already, if the system was installed in
    high-resolution mode and then Selective Install was run to return to VGA
    mode.)

    For XGA, the diskettes need to be searched for WINXGA and *G.FON.  The
    following shows the sequence of entries:

        DIR A:WINXGA
        DIR A:*G.FON

    No XGA drivers were on this diskette, but one of the font files was.
    Although the font file is not in a bundle of files, it is still in packed
    format and must be unpacked.

    The files are packed with their standard target directory coded into the
    packed file.  To copy the file to the system disk in the proper directory,
    just run the Unpack utility program.

        UNPACK A:SYMBOLG.FON

    This procedure continues until all of the scalable fonts are unpacked.
    These fonts are:

   o SYMBOLG.FON
   o TMSRG.FON
   o COURG.FON
   o HELVG.FON

    Eventually the WINXGA file is found by the dir a:WINXGA search.  It
    contains the WIN-OS/2 XGA.DRV and three XGA fonts.

        UNPACK A:WINXGA

    With all of the required driver and font files on the system disks, the
    next step is to modify the SYSTEM.INI file.

 4. Edit the SYSTEM.INI file and find the following line:

        display.drv=vga.drv

 5. This line specifies what device driver WIN-OS/2 is to use in full-screen
    sessions. Change this line to point to the high-resolution device driver
    that was unloaded in the steps above. In this example, the device driver is
    XGA.DRV.  The modified line should look like the following:

        display.drv=xga.drv

    Both SYSTEM.INI and WIN.INI have font entries that must be changed.  In
    SYSTEM.INI, these entries are:

        fixedfor.fon=vgafix.fon
        oemfonts.fon=vgaoem.fon
        fonts.fon=vgasys.fon

    For XGA, these entries must be changed to:

        fixedfor.fon=xgafix.fon
        oemfonts.fon=xgaoem.fon
        fonts.fon=xgasys.fon

    In WIN.INI, the entries:

        Symbol 8,10,12,14,18,24 (VGA res)=SYMBOLE.FON
        Helv 8,10,12,14,18,24 (VGA res)=HELVE.FON
        Tms Rmn 8,10,12,14,18,24 (VGA res)=TMSRE.FON
        Courier 10,12,15 (VGA res)=COURE.FON

    Must be changed to:

        Symbol 8,10,12,14,18,24 (XGA res)=SYMBOLG.FON
        Helv 8,10,12,14,18,24 (XGA res)=HELVG.FON
        Tms Rmn 8,10,12,14,18,24 (XGA res)=TMSRG.FON
        Courier 10,12,15 (XGA res)=COURG.FON

When these changes have been made and the INI files saved, the system is ready
for running Windows applications in WIN-OS/2 window sessions (VGA mode) and
WIN-OS/2 full-screen sessions (high-resolution mode).

For 8514 displays, you must delete the following line from CONFIG.SYS:

DEVICE=C:\OS2\MDOS\V8514A.SYS

For 8514 displays, the files to find are:

o WIN8514 (contains 8514.DRV, 8514SYS.FON, 8514OEM.FON, and 8514FIX.FON)
o COURF.FON
o TMSRF.FON
o HELVF.FON
o SYMBOLF.FON.

NOTES:

Windows developers should note that their debuggers work in full-screen only.
If you have a dual-monitor setup (8514+VGA), install OS/2 2.0 for the 8514 as
primary display with no secondary display.  This will allow your Turbo Debugger
for Windows (TDW) or CodeView for Windows (CVW) session to run full-screen on
the VGA display while the WIN-OS/2 session runs full-screen on the 8514.  For
CVW, make sure to use the /8 option.  Quick C runs on the same display as
WIN-OS/2.  If you use Quick-C, you don't need a special video configuration.

Installing OS/2 2.0 in this way will allow PM to run on the 8514, and your
full-screen debugger to run on the VGA.  It also will provide a "stereo" effect
for all full screen sessions; both the 8514 and VGA will show the same picture,
unless a full-screen application takes advantage of video-specific features.


ΓòÉΓòÉΓòÉ 9. Hardware Considerations ΓòÉΓòÉΓòÉ

Related Information:

o Personal Computer Manufacturers--Systems
o Adaptec and Future Domain SCSI Support
o OS2SCSI.SYS Replaces SCSI.SYS
o SCSI CD-ROM Support
o SCSI Removable Media Support
o SCSI Usage Notes
o AMI SCSI Adapters
o Formatting Diskettes
o CD-ROM Selective Install


ΓòÉΓòÉΓòÉ 9.1. Personal Computer Manufacturers--Systems ΓòÉΓòÉΓòÉ

OS/2 2.0 is supported on personal computers with an 80386 SX (or compatible) or
higher processor, with at least 4MB of memory and a 60MB hard disk with 15MB to
30MB of free space.

IBM is currently testing personal-computer manufacturers (PCM) systems for
compatibility with OS/2 2.0.  The compatibility test verifies 18 key functions
of OS/2 2.0.  Test results are based on selected model configurations provided
by the manufacturers. While testing is continuing, current compatibility
information about tested systems is available through your dealer or Marketing
Representative, as well as through the following:

o Prodigy (call the appropriate phone number for your area, or Membership
  Service at [phone]).

o CompuServe (call the appropriate phone numbers for your area, or Membership
  Service at 1-800-848-8199).

o IBM National Support Center Bulletin Board System (NSC BBS).  This service is
  available 24 hours a day, on a toll-call basis, with no access charge, to
  anyone in the world who has a modem, asynchronous-communication software, and
  a switched telephone line.  (The modem should be set for 8 data bits, 1 stop
  bit, no parity, and the standard transmission speed from 1200 to 9600 baud.)

  To access the NSC BBS, call [phone].

o IBM Link.  Eligible customers can obtain installation and usage assistance
  through IBM Link Question Support.  To obtain information about eligibility,
  contact your local Branch Office or Marketing Representative.

NOTE:

The compatibility test information is provided for information purposes only.

IBM MAKES NO WARRANTY, EXPRESSED OR IMPLIED, WITH RESPECT TO THE OPERATION OF
THE PERSONAL COMPUTERS LISTED THROUGH THE ABOVE SOURCES


ΓòÉΓòÉΓòÉ 9.2. Adaptec and Future Domain SCSI Support ΓòÉΓòÉΓòÉ

Device support for the following Adaptec and Future Domain SCSI adapters is
shipped with OS/2 2.0.  When any of the following adapters is installed in a
workstation, its presence is normally detected automatically, and the
appropriate device support is subsequently installed.  For reference, the names
of the device drivers that support each adapter are provided here:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéSCSI Adapter or Interface        ΓöéDevice DriverΓöé
Γöé                                 Γöéfilename     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AIC 6260                 ΓöéAHA152X.ADD  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1510                 ΓöéAHA152X.ADD  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1520/1522            ΓöéAHA152X.ADD  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1540/1542            ΓöéAHA154X.ADD  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1640                 ΓöéAHA164X.ADD  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1740/1742/1744       ΓöéAHA154X.ADD  Γöé
Γöé(Standard mode operation)        Γöé             Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAdaptec AHA 1740/1742/1744       ΓöéAHA174X.ADD  Γöé
Γöé(Enhanced mode operation)        Γöé             Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFuture Domain TMC-850/860/875/885ΓöéFD8XX.ADD    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFuture Domain TMC-1660/1670/1680 ΓöéFD16-700.ADD Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFuture Domain MCS-600/700        ΓöéFD16-700.ADD Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFuture Domain TMC-850IBM         ΓöéFD850IBM.ADD Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The TMC-850/860/875/885 and TMC-850IBM adapters will not be detected when the
adapter's BIOS is disabled.  You can manually install this support in your
system by following the steps below.

NOTES:

"xxxxxxxx.ADD" should be replaced with the file name of the device-driver file
you want to install.

 1. Locate Installation Diskette 8, which contains the file, DASDDRVS.

 2. Insert the diskette in drive A.

 3. Change the current directory to the root directory of the startup drive.

 4. Type:

        UNPACK A:DASDDRVS \OS2 /N:xxxxxxxx.ADD

 5. Add the following line to the CONFIG.SYS file:

        BASEDEV=xxxxxxxx.ADD

 6. Restart the system.


ΓòÉΓòÉΓòÉ 9.3. OS2SCSI.SYS Replaces SCSI.SYS ΓòÉΓòÉΓòÉ

The device driver, SCSI.SYS, has been replaced by OS2SCSI.SYS.  OS2SCSI.SYS is
provided in the \OS2 directory of the boot partition.  Any CONFIG.SYS entries
of the form

DEVICE=SCSI.SYS

should be replaced by the entry

BASEDEV=OS2SCSI.SYS

Normally, this is done automatically.

The OS2SCSI.SYS device driver is required for a number of SCSI CD-ROM devices,
SCSI Read/Write Optical devices, and SCSI Tape devices.


ΓòÉΓòÉΓòÉ 9.4. SCSI CD-ROM Support ΓòÉΓòÉΓòÉ

The SCSI CD-ROM support built into OS/2 2.0 has some manufacturer-specific
dependencies at this time.  Support has been verified for IBM and Toshiba SCSI
CD-ROM drives.  Information about the support and verification of additional
manufacturers' drives will be made available at a later date.


ΓòÉΓòÉΓòÉ 9.5. SCSI Removable Media Support ΓòÉΓòÉΓòÉ

Full function support is not yet available for SCSI hard disk drives that
support removable media.  Examples of this class of device include the
"Bernoulli" drives manufactured by IOMEGA, and the removable-media drives
manufactured by SyQuest Technology.

Although OS/2 2.0 recognizes these drives, it will treat media as large
diskettes.  You will be able to format for the FAT file system only.  You will
not be able to partition or start up from the media, and partitioned media will
not be recognized.

If the IBMINT13.I13 driver is used to control these units, the drive will be
treated as a fixed drive.  In this case, the cartridge must be in the drive at
startup time, and you will need to use the Shutdown procedure to remove the
cartridge from the drive.


ΓòÉΓòÉΓòÉ 9.6. SCSI Usage Notes ΓòÉΓòÉΓòÉ

Following are a number of notes about usage, and about potential compatibility
problems with the microcode levels on various adapters and devices.

Adapter: All Adaptec adapters
Note: SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to
start up from that hard disk.

Adapter: Adaptec AHA-154x
Drive: IBM 0661 - 320MB SCSI
Note: Adapter BIOS will not recognize the drive as Target 0 or 1 (Drives 80,
81).  For OS/2 2.0, the drive can be used as a non-startup drive.

Adapter: All Adaptec adapters
Note: SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to
start up from that hard disk.

Adapter: Adaptec AHA-154x
Drive: IBM 0661 - 320MB SCSI
Note: Adapter BIOS will not recognize the drive as Target 0 or 1 (Drives 80,
81).  For OS/2 2.0, the drive can be used as a non-startup drive.

Adapter: Adaptec AHA-174x
Drive: IBM WDS-3180 - 80MB SCSI, IBM WDS-3160 - 160MB SCSI
Note: Adapter will not recognize these drives when configured in 'STANDARD
MODE' (AHA-154x emulation).  Instead, the AHA-174x adapter should be configured
in 'ENHANCED MODE'.  This mode is supported by the OS/2 2.0 drivers, and the
problem does not occur when the adapter is operating in enhanced mode.

Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0.
          Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0.
System: IBM Models 35 and 40 when the Future Domain adapter is controlling the
startup diskette.
Note: Will produce the message, "Disk read error has occurred" when you attempt
to start the Installation diskette.  Contact Future Domain for a free BIOS
upgrade.


ΓòÉΓòÉΓòÉ 9.7. AMI SCSI Adapters ΓòÉΓòÉΓòÉ

AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized
as Adaptec adapters.  If you have one of these adapters in your system, do the
following:

o At the final restart after the installation is complete, delete from the
  CONFIG.SYS file, any line with

    BASEDEV=AHA1xxx.ADD
   (where "x" can be any character).

  from the CONFIG.SYS file.

o Ensure the line

    BASEDEV=IBMINT13.I13

  appears in the CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 9.8. Formatting Diskettes ΓòÉΓòÉΓòÉ

If you have a non-Micro Channel system with a 5-1/4" drive and its 3-1/2"
drives all support media sense, your 5-1/4" drive will format diskettes at
720MB.  Previously formatted 1.2MB diskettes will read and write correctly.  A
fix for this problem can be obtained from the electronic bulletin board
described in the "Service and Support Information" section of this file.


ΓòÉΓòÉΓòÉ 9.9. CD-ROM Selective Install ΓòÉΓòÉΓòÉ

When installing CD-ROM using "Selective Install", do not install other options
at the same time.


ΓòÉΓòÉΓòÉ 10. Trademarks and Service Marks ΓòÉΓòÉΓòÉ

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

IBM
Operating System/2
OS/2
Presentation Manager
WIN-OS/2
XGA

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

Microsoft, Microsoft Bookshelf, Microsoft Excel, Microsoft Flight Simulator,
Microsoft 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.


ΓòÉΓòÉΓòÉ <hidden> About the author ΓòÉΓòÉΓòÉ

This document was formatted using IBM's IPF compiler by Michael Kaply.

Please send correspondence to:

Michael Kaply
IBM (04-05-30)
5 W. Kirkwood Blvd.
Roanoke, TX 76299-0001

or

Internet: [e-mail]
Prodigy: MVMF10A
IBM: MIKEK at DALHQIC2


ΓòÉΓòÉΓòÉ <hidden> Team OS/2 ΓòÉΓòÉΓòÉ