OS/2 Shareware BBS: SysTools/SysTools.zip/pcmdoc.zip/PCMDOC40.INF

OS/2 Help File | 1996-10-26 | 83KB | 2,928 lines

ΓòÉΓòÉΓòÉ 1. OS/2 COMPATIBILITY TEST PROGRAM ΓòÉΓòÉΓòÉ

Purpose

The purpose of the OS/2 Compatibility Test Program is to offer a test process
that ensures Systems and Motherboards/CPU's are compatible with OS/2.
Primarily, this program is for system and motherboards/CPU's manufacturers.


ΓòÉΓòÉΓòÉ 1.1. Test Kit Materials ΓòÉΓòÉΓòÉ

The compatibility test process starts with the delivery of the test kit package
which consists of the following

   1. Complementary copy of OS/2 V 4.0 on CD-ROM (see note)

   2. OS/2 compatibility Test Kit V 4.0 CD-ROM (with documentation).

   3. Device Driver Pak On CD-ROM.

   4. Microphone for Speech Recognition Test.

   5. OS/2 Installation Instructions.

   6. OS/2 License Agreements and License Agreement Information Booklet.

   7. Compatibility Test Kit License Agreement.

   8. OS/2 Approved  Ready Logo Agreement.

   9. Welcome Letter and Testkit Documentation Print Instructions.

 Note  This customized copy of OS/2 Warp V4.0 does not include Lotus Notes Mail
 4.1 or the Application Sampler CD which is provided in the retail version of
 Warp V 4.0. Please disregard all references to the Lotus Notes Mail and
 Application Sampler products in the License information booklet and other
 documentation in this package. All other terms and conditions remain in
 effect.

 Once the test kit materials are received,you will have everything

   you need to load OS/2 and to run the tests.


ΓòÉΓòÉΓòÉ 1.2. Test Documentation ΓòÉΓòÉΓòÉ

This documentation will guide you through each test.  Each test is unique and
can be referenced by test number.


ΓòÉΓòÉΓòÉ 1.3. Test Duration ΓòÉΓòÉΓòÉ

Selecting all tests to execute, the run time is about one (1) day.  This will
include setup time. The run time is directly related to the amount of RAM
installed in the test system. This will be noticed especially in the STRESS
test.  Bench marking the STRESS test, the following results were recorded.

     TEST # 10 STRESS, 486/33MHz  16MB RAM  RUN TIME = Approx 5 hours

     TEST # 10 STRESS, 486/66MHz  8MB RAM  RUN TIME = Approx 7 hours
 Each test has been documented as to the run time on the following pages.
 Please run all the tests from beginning to end.


ΓòÉΓòÉΓòÉ 1.4. Test Results ΓòÉΓòÉΓòÉ

When tests are complete, the test results are copied to a Test Results Diskette
and the diskette is sent to the program office.

Once the test results are received at the program office, they will be verified
and you will be faxed the test report. When tests are successful, you will
receive a letter confirming OS/2 compatibility and the systems are entered into
the next update of the OS/2 Hardware Compatibility List.

When you are ready to collect test results from the test system, please read
the chapter on COLLECTING TEST RESULTS.


ΓòÉΓòÉΓòÉ 1.5. Tests Required for OS/2 Compatibility ΓòÉΓòÉΓòÉ

The OS/2 compatibility test suite consists of (2) sections.

Section 1 is a collection of tests which are required to achieve OS/2
Compatibility.These tests include installation and initialization of OS/2,
batch testing, stress testing, hardware interface tests, and special function
tests like multimedia.

Section 2 contains a set of optional tests.  For example

   1. Advanced Power Management

   2. SMP Verification

   3. PCMCIA

   4. SPEECH RECOGNITION

 These tests will only be required for compatibility if the system that is
 being tested will support the specific function.


ΓòÉΓòÉΓòÉ 1.6. Before You Begin Testing ΓòÉΓòÉΓòÉ

The OS/2 Compatibility Test package is intended to be installed and run on a
stand alone system.  A stand alone system is not connected to any other system
or network.

Hard Disk Drive Selection

OS/2 Warp V 4.0 is intended to be installed on the boot partition drive. Please
refer to the OS/2 Installation Guide for installation instructions. The C
drive is used for all examples herein.

The Compatibility Test Kit can be installed on any local (non networked) drive.
The D  Drive is used for all examples herein. The selected drive should be
formatted prior to installing the Test Kit, with either FAT or HPFS file
system. When you install OS/2, select the Advanced Installation option to set
the OS/2 and Test Kit Partitions The OS/2 Partition should be a boot partition,
set "installable", with a minimum of 250 Meg. The Test Kit partition should be
a logical drive with a minimum of 130 Meg. Make the partitions as large as disk
space permits. Allow at least 30 Meg for the Swapper, swapper.dat on the boot
drive in addition for the space for OS/2 and use the remaining disk space for
the Testkit partition.


ΓòÉΓòÉΓòÉ 1.7. Test System Configuration ΓòÉΓòÉΓòÉ

Hardware Requirements

The minimum hardware configuration to load OS/2 is

     System unit to be an 486sx or above

     System unit to have at least 16 MB RAM

     OS/2 partition for Installation and Initialization, 250 Mb min. (an
      additional 30 Mb is recommended for SWAPPER.DAT)

     A mouse is required

     A printer is to be installed even if no printer is attached.

     The Test Kit logical drive needs at least 130MB free to accommodate all
      the tests.

     Mulit Media Sound Support (if system is shipped configured for
      multi-media)

     CD-ROM drive (reqired for OS/2 and Test Kit Installation)

 Note:  The Multimedia tests is the largest segment of the test cases and
 requires 96Mb free.

 Software Requirements

 You should have the following operating system software

     OS/2 Warp, V 4.0 or OS/2 Warp Server V4.0 for SMP

     OS/2 Compatibility Test Kit V 4.0

 Other Items

     Two blank diskettes, not provided.

     Music CD (for Multimedia test), not provided


ΓòÉΓòÉΓòÉ 1.8. Contacts  (OS/2 Compatibility Test Program Office) ΓòÉΓòÉΓòÉ

A central program office is available for support at the following locations

For North America, Canada, South America, or Asia Pacific, the program office
and support is as follows

               OS/2 Compatibility Test Program Office

               Phone  [phone]  (test results  technical support)

               Fax  [phone] (all correspondence)
           MAIL TEST RESULT DISKETTES TO

                Bob Ranta

                OS/2 Compatibility Program Office

                IBM Corporation m/s 9623

                11400 Burnet Road

                Austin TX, 78758 USA

 Contact Information cont'd)

 For Europe, Middle East, and Africa, the program office and support is as
 follows

               Primary correspondence  Internet - [e-mail]

               Paul Nolan - Primary Contact - Internet -
                [e-mail]

               Tel  44 (UK) 1256 343145

               Fax  44 (UK) 1256 58684

               Dave Lock - Secondary Contact- Internet - [e-mail]

               Tel  44 (UK) 1256 341405

               Fax  44 (UK) 1256 58684

               File Exchange BBS  44 (UK) 1256 336991

               IBM Europe web home page  http //www.europe.ibm.com

               IBM PSM Europe ftp site  ftp.europe.ibm.com

           MAIL TEST RESULTS DISKETTES TO

                Paul Nolan

                OS/2 Compatibility Test Program Office

                IBM UK Ltd

                Normandy House, Alencon Link

                Basingstoke, England

                RG21 1EJ

 Problem Reporting

 When reporting problems to the program office, for either the OS/2
 Compatibility Test Kit or with the  OS/2 software, there is certain
 information that is needed to work the problem.  Please see the chapter on
 Problem Reporting.




ΓòÉΓòÉΓòÉ 1.9. OS/2 SYSTEM INSTALLATION and INITIALIZATION ΓòÉΓòÉΓòÉ

PURPOSE

Follow the instructions for installation provided with OS/2 Warp V 4.0. These
instructions are provided relative to the Compatibility Test Kit V 4.0.

Note:  OS/2 Warp V 4.0 does not require Windows Software to be installed first.

For OS/2 Warp Version 4, there are two install options

   1. EASY Installation

   2. ADVANCED Installation(RECOMMENDED)

      Note:  Advanced install is recommended because it provides the
      opportunity to partition the hard file (FDISK UTILITY) as required.

 Process

 There are three phases of installation followed by system reboot.

   1. Phase 1-  Diskette 0 (Installation Setup)

   2. Phase 2 - Diskette 1 (Operating System Installation)

   3. Phase 3 - Diskette 2 (System Configuration)

   4. System Reboot (You will format Testkit drive after reboot)

 Phase 1

   1. Insert the Installation diskette into the A  drive and press CTRL-ALT-DEL

   2. You will see a blue screen. Follow follow the directions on the screen.

 Phase 2

 You will need to create at least 2 partitions during installation, one for the
 operating system, and one for the Testkit.

   1. Install OS/2 on any letter drive. The C  drive must always be a Primary
      Partition (DOS requirement). For any other drive letter, the partition
      should be a Logical Drive. For examples provided herein, Drive C  will
      contain the operating system (recommended).

   2. Format the drive. If this is the very first time OS/2 is installed, you
      must choose to format drive that OS/2 will be installed on. The file
      system can be either FAT or HPFS.

 Phase 3

   1. Follow the Prompts to set your system configuration.

   2. Select a printer in phase 3, otherwise problems will be encountered in
      TEST #10 (STRESS TEST), TEST #8 (SNFMVDM) and TEST #15 (PRINTDD).


   3. After phase 3 of installation completes, the system will shutdown and
      reboot. Check for the printer icon on the desktop.

 System Reboot

 When the system is restarted the Welcome Panel is displayed.

   1. Read through the entire tutorial for OS/2 Warp V 4.0 even if you are
      considered a "Guru" on Version 3. There are a lot of new functions and
      features in Version 4.

   2. Click on the tool bar and select Command Prompts from the pull-down menu.

      During OS/2 installation, your boot partition/drive was formatted. You
      must now format the logical/drive you selected for the Testkit
      installation.

   3. Type Format <drive letter>  /fs < FAT|HPFS> /v.

      Example  Format D  /fs FAT /v

 The Installation and Initialization process is completed. You are now ready to
 install the Testkit.


ΓòÉΓòÉΓòÉ 1.10. OS/2 BonusPak Changes ΓòÉΓòÉΓòÉ

The Bonus Pak Function (CD) in Warp V 3.0 has been incorporated into the base
on Warp V 4.0. Therefore there is no longer a Bonus Pak CD to install. The
System Information Tool that was required in V 3.0 is no longer needed in V
4.0. There is now a utility in the OS2 System\System Setup Folder call the
Hardware Manager that provides system information.


ΓòÉΓòÉΓòÉ 1.11. SUMMARY OF TEST RUN TIME ΓòÉΓòÉΓòÉ

The following table itemizes all of the tests in the testkit, their runtime,
and purpose.

┤ББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББББЖ
В SUMMARY OF TESTS (RUN TIMES APPROXIMATE)                                     В
╙БББББББББББББББББББСБББББББББББББББББББСБББББББББББББББББББСББББББББББББББББББЙ
В TEST 1            В OS/2 System       В 60 Minutes        В SNF001           В
В                   В Installation      В                   В                  В
В                   В Initialization    В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 2            В File I/O Using    В 10 Minutes        В SNF002           В
В                   В Semaphores Test   В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 3            В Collating         В 3 Minutes         В SNF005           В
В                   В Sequence   Case   В                   В                  В
В                   В Mapping Test      В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 4            В Code Page         В 5 Minutes         В SNF006           В
В                   В Switching         В                   В                  В
В                   В (VIDEO/PRINTER)   В                   В                  В
В                   В Test              В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 5            В Shared Segments   В 5 Minutes         В SNF007           В
В                   В Test              В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 6            В High Performance  В 5 Minutes         В SNFBPB           В
В                   В File System Test  В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 7            В Batch Processing  В 3 Minutes         В SNFREXX          В
В                   В   REXX Calls      В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 8            В Automated Tests   В 15 Minutes        В SNFMVDM          В
В                   В To Stress The     В                   В                  В
В                   В Base System       В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 9            В Your DOS          В 30 Minutes        В SNFWIN           В
В                   В Windows** Appli-  В                   В                  В
В                   В cations Test      В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 10           В Stress Test       В 4 to 5 hours      В PCMMED01         В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 11           В Keyboard Device   В 15 Minutes        В KBD              В
В                   В Driver Test       В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 12           В Disk Multi-       В 20 Minutes        В FVTDISK          В
В                   В Tasking Test      В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 13           В Format Utility    В 15 Minutes        В FORMAT           В
В                   В Test              В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 14           В Timer Device      В 51 Minutes        В TIMERDD          В
В                   В Driver Test       В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 15           В Printer Device    В 20 Minutes        В PRINTDD          В
В                   В Driver Test       В                   В                  В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 16           В OS/2 Multi-Media  В 10 Minutes Each   В PCM_VGA,PCM_SVGA,ВCM_HPFS,
В                   В Test              В                   В                  В
В                   В                   В                   В PCM_CD,PCM_CDS,PCВ_FLC,
В                   В                   В                   В                  В
В                   В                   В                   В PCM_REXX         В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 17           В APM Test          В 60 Minutes        В SNFAPM           В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 18           В PCMCIA TEST       В 30 Minutes        В SNFPCM           В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 19           В OS/2 for SMP Test В  >1 Minute        В SNFSMP           В
╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
В TEST 20           В Voice Navigation  В 30 Minutes        В SPEECH           В
БББББББББББББББББББ╔БББББББББББББББББББ╔БББББББББББББББББББ╔ББББББББББББББББББД


ΓòÉΓòÉΓòÉ 1.12. TESTKIT INSTALLATION ΓòÉΓòÉΓòÉ

If at any time there is a request to remove the test kit code from the test
machine, type at the C prompt REMVKIT

Pre-Requisite

Note:  Set the date and time of the test system compac.

     Type TIME and enter the current time

     Type DATE and enter the current date

 IMPORTANT  When loading test cases, it is recommended to load all the test
 cases at the same time. However, if the Testkit partition available space is
 constrained (less than 130 Mb), you can wait to load Multimedia tests later.

 The tests in this test kit can be installed on any local/logical drive,
 however, the D  drive is preferred and is used for all examples in the
 documentation.  The selected testkit drive can be re-formatted with this
 process. CONFIG.SYS is modified during Testkit install which will require the
 system to be SHUTDOWN and rebooted after test cases are loaded.

  REMINDER! Please read all of the Testkit documentation before starting test.

 Testkit Installation Procedure

   1. Insert the OS/2 Compatibility Test CD-ROM in the CD-ROM drive.

   2. Click on the Toolbar icon "Command Prompts" and open an OS/2 window from
      the pull-down menu.

   3. Change to the PCM_INST directory on the CD-ROM and type INSTALL

   4. Wait, INSTALL will display a Presentation Manager (PM) window "PCM
      Testing Setup - Main Menu".

      On this screen default selections are  compac.

          OS/2 Boot Partition = C

          Test Case Partition = D

          OS/2 Release = 4.00

          Format Testcase Partition = NO  (Change to YES only if you are
           reformatting this partition)

          Install PCM Test kit From (Diskette or CD-ROM Drive)

          Format Type = FAT (or HPFS)

   5. To change the defaults, select  CONFIGURE  which will display the "PCM
      Testing Configuration" panel. On this panel the default selections can be
      changed for  compac.

          OS/2 Boot Partition

          Test Case Partition

          OS/2 Release/Driver Level

          Format Testcase Partition

          FAT or HPFS

          Source Drive for PCM Test Kit INSTALLATION

   6. Click on ACCEPT to save your changes and return to the Main-Menu. Verify
      your selections. compac.

          Select Update/Verify CONFIG.SYS, STARTUP.CMD, AUTOEXEC.BAT

          Select all applicable test cases

          You will be prompted for THE CD-ROM or DISKETTE test cases to be
           installed.

          Click on RUN when you have completed all selections. If you selected
           Multimedia, it will take approx 15-20 minutes to install

           Note:  PCMCIA, SMP, APM, and SPEECH tests are only for systems
           supporting these features.

      Note:  After each of the various test cases are installed, a message will
      be displayed to confirm completion.  It is suggested that you verify your
      selection of test cases as these messages are displayed. PLEASE DO NOT
      USE THE MOUSE OR KEYBOARD until you see the message "PCM Test kit
      Installation Complete".

   7. Click on DONE, after selected test cases are installed

   8. Click OK in Window 'PCMSETUP Activity Completed

   9. Click on EXIT or Select additional test cases to load

  10. Click OK

  11. Using the Toolbar, select SHUTDOWN and reboot the system (CTRL-ALT-DEL).


ΓòÉΓòÉΓòÉ 1.13. TO Create Diskettes from CD-ROM ΓòÉΓòÉΓòÉ

Process

Please use this process only if you are going to install the test cases from
diskettes. This process will not copy the Multimedia tests to diskettes. For
loading the test system, the Multimedia tests can only be run by installing
those test cases from the OS/2 Compatibility Test Kit CD-ROM that came with
this package.

If you are installing on a system with SOUND SUPPORT, Multimedia tests are
required. If sound support is available, we suggest loading test cases from a
parallel port CD-ROM or a docking station CD-ROM, or over a network connection.

To create 3.5" diskettes, TYPE MAKE_350 in the DSKTIMGS directory of the
CD-ROM.

To create 5.25" diskettes, TYPE MAKE_525 in the DSKTIMGS directory of the
CD-ROM.

To create individual diskettes type the following information for each diskette
you need compac.

Note:  Assume CD-ROM is F  Drive and target drive is 3.5 diskette in the A
Drive.

   1. F

   2. CD DSKTIMGS

   3. LOADDSKF F \DSKTIMGS\350\FILENAME A  compac.

          Where FILENAME is  SETUP.DSK

          Where FILENAME is  ACCEPT1.DSK

          Where FILENAME is  ACCEPT2.DSK

           Note:  If testing Warp 3.0 use 3ACCEPT2.DSK instead of ACCEPT2.DSK

          Where FILENAME is  ACCEPT3.DSK

          Where FILENAME is  STRESS1.DSK

          Where FILENAME is  STRESS2.DSK

          Where FILENAME is  STRESS3.DSK

          Where FILENAME is  STRESS4.DSK

          Where FILENAME is  FVT1.DSK

          Where FILENAME is  FVT2.DSK

          Where FILENAME is  EXTEN1.DSK    (abbreviation for extension)

          Where FILENAME is  EXTEN2.DSK    (abbreviation for extension)

 Note:  You can not create diskettes for the Multimedia test.  That test
 requires installation to be done from the CD-ROM.


ΓòÉΓòÉΓòÉ 1.14. Bulletin Board and World Wide Web Information ΓòÉΓòÉΓòÉ

Bulletin Board System You can access the PCM/IHV Bulletin Board System (BBS)
and down load a Test Kit Tips file which contains information about The OS/2
Compatibility Test Program and testcases.

When the Test Kit Tips are down loaded, you can look through this information
by test name.  Once you have found the test in question, the information which
is presented represents the latest information that is available about the test
case.  This information may help you resolve your test results.

Other files that are available may be command files.  These files are
originally shipped on the CD-ROM.  However, if updates are necessary, these
files will be also available.  You should down load all command files and
replace the ones you are using that came with the CD-ROM.

The procedure described in this documentation will enable the test kit user to
down load the latest information regarding test cases in this test kit.

The BBS system is accessed using a PC and modem to connect to 512-838-9717. The
BBS system will support up to 14.4Baud.

Once connection is made, down load the file TESTHELP.ZIP and hang up.

Note:  This file is on the CD (TESTHELP.KIT) and gets copied to the OS/2
directory on the boot drive when you install the testkit. For the latest copy
you can access the BBS.

Process

     Enter your name as TEST

     Enter your last name as KIT

     When asked to verify enter Y

     Enter password as WARP

     Hit ENTER (three times)

     When asked to view next bulletin, respond with N

     Enter F for FILE

     ENTER D for DOWNLOAD

     ENTER Z for ZMODEM

     ENTER TESTHELP.ZIP to download ZIP file

     Enter G to LOGOFF when download is complete.

      Note:  The ZIP file will need to be un packed with PKUNZIP as there may
      be multiple files downloaded.
 World Wide Web

 The OS/2 Compatibility List is now maintained on the World Wide Web. We will
 eventually migrate the Bulletin Board information to the Web with additional
 program information, FAQ's, problem reporting, and Maintenance Updates for the
 Testkit.

 The URL for the Web is http \\austin.ibm.com/pspinfo/os2hw.html


ΓòÉΓòÉΓòÉ 1.15. SYSTEM HARDWARE CONFIGURATION ΓòÉΓòÉΓòÉ

Information about your test system configuration is required.

When ready, open the folder PCM KIT on the Desktop and then select the folder
PCM HDW.

A screen display for the system hardware configuration is presented. When the
first screen is complete, click on 'Continue' to see the following pages.

When complete, click on 'Save and Exit'

If changes are required, run again, i.e., click on PCM HDW to see entries and
make changes. The file, MACHINE.TXT, is created and saved in C \PCMLOGS.


ΓòÉΓòÉΓòÉ 1.16. RUNNING TEST CASES ΓòÉΓòÉΓòÉ

From the PCM KIT folder, double click on the folder "PCM TEST". The "Test
Selection  Control" PM window is displayed.

IMPORTANT!

Tests should always be run from the window that is now displayed. The
individual test documentation can be used when rerunning a single test
(manually) for best results.

There are a few tests that require manual intervention (keyboard entry) and you
have the option of running these tests FIRST or LAST. First will run the manual
tests first. Last will run the manual tests last.

The test cases have been grouped by type and by clicking on the box for that
group, all tests of the same type will be run. The selections are

   1. Select, FIRST or LAST (Suggest FIRST)

   2. Select, Execute ACCEPTANCE Testcases

   3. Select, Execute STRESS Testcases

   4. Select, Execute FVT Testcases

          Select, 3.5" or 5.25" diskettes

          Enter a Physical Drive Number (any local drive)

          Enter A Logical Drive Letter (any local drive)

   5. Select, Execute Multimedia

      Note:  If the test system is shipped with either a sound card or a
      CD-ROM, select Multimedia. If you installed a CDROM drive in the system,
      or used a CDROM drive connected to the Parallel Port to install OS/2 and
      the Testkit, but the CDROM drive is not in the shipped configuration,
      remove the CDROM support before proceeding. Go into the System
      Setup\Install/Remove folder and select "Selective Uninstall". You can
      alternately edit the config.sys file in the boot drive to remove the
      CDROM device driver statement (DEVICE=).

      If the test system supports sound and if......

          The test drive is formatted HPFS, then select, PCM_HPFS or

          The video is set to VGA, then Select, PCM_VGA

          The video is set to SVGA, then Select, PCM_SVGA (1024x768x256 min
           resolution)

          Select PCM_FLC.

          Select PCM_REXX.

          Select PCM_CD for systems shipped with a regular CD-ROM drive.

          Select PCM-CDS for systems with a STREAMING CD-ROM drive.

           Be certain a music CD (not supplied) is in the CD-ROM drive.

   6. Select, Execute PCMCIA testcases if appropriate and

          Select, 1st PCMCIA Slot and the appropriate boxes and buttons

          Select, 2nd PCMCIA Slot and the appropriate boxes and buttons

           Note:  Some systems will not re-boot with PCMCIA cards installed, or
           may leave the cards unusable if re-booted when installed. If this
           occurs with the system being tested, run PCMCIA testcases from an
           OS/2 Full Screen session, using the directions in the individual
           test documentation for PCMCIA testing.

   7. Select, Execute SMP Testcases (Requires OS/2 for SMP operating system
      software) Advanced Power Management.

   8. Select Exit or Help if you need more information about the selection
      choices.

   9. Select Run to begin the tests.


ΓòÉΓòÉΓòÉ 1.16.1. Top Down Test Case Flow ΓòÉΓòÉΓòÉ

The following grid will help to understand the flow of test case execution when
selections are made and RUN button pushed.

If LAST selected, manual tests will run last (after automated tests).

If FIRST was selected, manual tests will run first (recommended).

If FIRST was selected and.....

   1. If ACCEPTANCE was selected. Acceptance test case #8 SNFMVDM will start
      and require manual keyboard intervention.

   2. If FVT was selected, FVT manual test cases #11 KBD, and #15 PRINTDD will
      start and require manual intervention.

 Automated testing will then continue.... If ACCEPTANCE was selected automated
 test cases #1-7 will start.

          #1 SNF001 - Creates Machine.txt file from System Hardware
           Configuration Information entered by user previously.

          #2 SNF002 - File I/O Using Semaphores.

          #3 SNF005 - Coalating Sequence and Case Mapping.

          #4 SNF006 - Code Page Switching Video

          #5 SNF007 - Shared Segment.

          #6 SFNBPB - High Performance File System.

          #7 SNFREXX- Batch Processing and REXX calls.
 If FVT selected, the following automated testcases will start

          #12 FVTDISK - Disk Multitasking

          #14 TIMERDD - Timer Device Driver.

 If MULTIMEDIA was selected, #16 Multimedia automated tests will start.

        1. If VGA was selected, PCM_VGA will start.

        2. If SVGA was selected PCM_SVGA will start.

        3. If HPFS was selected PCM_HPFS will start.

        4. If CD was selected PCM_CD will start.

        5. If CDS was selected PCM_CDS will start.

           Note:  If Acceptance or FVT selected, reboot will occur prior to
           start of Multimedia test cases.

 If PCMCIA was selected the following automated testcases will start.

        1. If ATA was selected ATA will start.

        2. If FLASH was selected FLASH will start.

        3. If SRAM was selected SRAM will start.

           Note:  If Acceptance or FVT or Multimedia was selected, reboot will
           occur prior to start of PCMCIA test cases. PCMCIA will run for Slots
           1 AND/OR 2. At completion, If FVT or Multimedia was selected, e-boot
           will occur to continue SVT AND other tests

 If SMP was selected, #19 SMP Symmetrical Multi-Processor testcase will start.

 If STRESS was selected,

        1. You will be prompted to insert a DISKETTE into the A  drive.

        2. #10 PCMMED01 STRESS automated testcase will  start.

           Note:  If Acceptance, FVT, Multimedia, or PCMCIA was selected,
           reboot occurs prior to start of STRESS test.

        3. Starts PCMMED01

 If FVT was selected,

        1. You will be prompted to insert a DISKETTE into the A  drive.

        2. FORMAT test case will start.

        3. Automated testing completes and the system reboots.


ΓòÉΓòÉΓòÉ 1.16.2. Automatic Shutdown and System Re-start ΓòÉΓòÉΓòÉ

When running the tests from the PM WINDOW, the test system will SHUTDOWN and
REBOOT automatically when going from one group of tests to another. This action
is just as if someone hit CTRL-ALT-DEL on the keyboard.

The execution and completion of a group of tests just prior to the reboot may
be difficult to observe, but using the guidelines below, the Automatic Shutdown
and Reboot will happen under the following test combinations.

          When selecting STRESS test cases, the system will automatically
           SHUTDOWN and REBOOT whenever selecting the STRESS tests and any
           other test cases.

          When selecting PCMCIA test cases, the system will automatically
           SHUTDOWN and REBOOT whenever selecting PCMCIA tests and any other
           test cases.

          When selecting Multimedia test cases, the system will automatically
           SHUTDOWN and REBOOT whenever you have selected  MULTIMEDIA tests and
           any other test cases.

          If a test is run from the individual test documentation, for better
           results, please remember to re-boot the system prior to test
           execution.


ΓòÉΓòÉΓòÉ 1.16.3. Section 1 Tests (detail) ΓòÉΓòÉΓòÉ

ACCEPTANCE TESTS (#8, followed by #1-#7)

This flow assumes that you have selected the Acceptance test cases to RUN, and
the manual tests to run FIRST, the following will be observed

          The screen will momentarily go completely blank

          The screen will appear to pause at a DOS Full Screen prompt (D \VDM)

          A box will be displayed with flashing colors about 1 minute into the
           test.

          Again, the box of flashing colors will be displayed about 2 minutes
           into the test.

          After a full five (5) minutes, with the display of flashing colors,
           press Q and that part of the test will end.

           Note:  When this test starts, time it for five (5) minutes, then
           press Q

          The balance of the ACCEPTANCE tests will run without intervention.

          After each test in the Acceptance group completes and before the
           next test starts, the system will momentarily display the test
           results status.  This will go by very fast and you are not expected
           to observe or record this information

          If no other tests have been selected to run, control is returned
           with a prompt at an OS/2 Full Screen or to the Desktop

          At the end of all testing, see the process on Collecting Test
           Results

           Note:  The process to collect test results will verify all tests
           were run and passed.  At that time, a test summary will be displayed
           showing the results of the tests.  It is not required to manually
           verify test results.  However, those results can be viewed By keying
           TYPE PCMACCPT.SUM  from the D \BATCH directory, and a summary of
           Acceptance Tests will be displayed.

      STRESS TEST #10 (detail)

      Selecting the STRESS test to RUN, and manual tests are to be run FIRST,
      the following will be observed

          Just prior to the start of the STRESS test, if other tests were
           selected and have finished, an automatic system re-boot will occur.

          The system will prompt for a scratch diskette. Once inserted, press
           ENTER. STRESS test will run to completion without any further input.

          If no other tests have been selected to run, control is returned to
           an OS/2 Full Screen or to the Desktop.

          At the end of all testing, read the process "Collecting Test
           Results".

           Note:  The process to collect test results will verify all tests
           were run and passed.  At that time, a test summary will be displayed
           showing the results of the tests.  It is not required to manually
           verify test results, however, those results can be viewed by keying
           TYPE PCMMED1.SUM from the D \LOGM1 directory. A summary of STRESS
           Tests will be displayed.

      FVT TESTS (#11, #15 manual test followed by #12,#14 automated tests).

      KBD

      If other tests have also been selected to run, depending the selection,
      an automatic system reboot may occur.

          If the manual tests have been selected to run FIRST and RUN is
           clicked, the following may be observed

          A message will be displayed, PRESS ANY KEY TO CONTINUE , Respond by
           pressing any key.

           Note:  The above message will be displayed twelve (12) times, and
           the window may need to be enlarged to see the message at the bottom
           of the screen.

           Important!

           Please do not press ENTER until prompted, or the test will fail.

          Five (5) messages in sequence will be displayed about the key board
           lights, respond by pressing Y or N

        

      PRINTDD

      A message will be displayed Testing LPT1 in OS/2 mode...Press any key
      when ready, respond by pressing any key to continue

          A message will be displayed, Press any key when ready, respond by
           pressing any key to continue, about three (3) times

           Note:  A printer does not need to be physically attached to the test
           system for this test to be successful.  If a printer is not
           attached, an error message that indicates that the printer is not
           responding.... There is a problem with your printer.  Check the OS/2
           Desktop for more information....PRESS ANY KEY TO CONTINUE, but do
           not return to the Desktop while test is running. This dialog box
           will appear periodically. Just hit any key to continue.

          Upon completion, select Cancel if prompted.

           FVTDISK (runs automated)

      FORMAT

          Insert a blank diskette when prompted by a Diskette Request dialog
           box and press ENTER

           Note:  The diskette will be scanned for up to ten (10) minutes.

          If no other tests have been selected to run, control is returned
           with a prompt at an OS/2 Full Screen or to the Desktop

          At the end of all testing, see the process on Collecting Test
           Results

           Note:  The process to collect test results will verify all tests
           were run and passed.  At that time, a test summary will be displayed
           showing the results of the tests.  It is not required to manually
           verify test results.  However, those results can be viewed By keying
           TYPE FVTSECT2.SUM  from the D \LOGF directory, and a summary of FVT
           Tests will be displayed.

      MULTIMEDIA TESTS

      If selected, the Multimedia test cases will run to completion without
      keyboard intervention.  A complete description of the selection and
      execution of the multimedia tests is documented as TEST#16. PCM_REXX
      requires manual intervention to close PMREXX at completion.


ΓòÉΓòÉΓòÉ 1.16.4. Section 2 Tests ΓòÉΓòÉΓòÉ

ADVANCED POWER MANAGEMENT

SMP

PCMCIA

SPEECH

Section 2 tests (except PCMCIA) are manual tests. Please read the individual
test case documentation to see if these tests will be required.


ΓòÉΓòÉΓòÉ 1.17. COLLECTING TEST RESULTS ΓòÉΓòÉΓòÉ

PURPOSE

To collect test results and to create a Test Results Diskette, which when
verified, will be mailed to the program office.

When tests that were selected to run have completed, results are now ready to
be collected.  The collection of test results can be done at any time after
testing is complete or after a re-run of an individual test.

Please verify that data entry for the System Hardware Configuration has been
completed before collecting test results. If not, an error will be posted for
TEST # 1 when this process completes. Data entry for System Hardware
Configuration is started by clicking on the Desktop icon, PCM KIT and then PCM
HDW.  This can be done at any time, but must be complete before results are
collected.

On the Desktop, from the PCM KIT folder, select the icon PCM RESULTS, which
will bring up a "Testkit / System Information" window.

Note:  The information requested is very important because the system
manufacturer and model name are used for the entry into the monthly publication
"OS/2 Hardware Compatibility List".  These names will appear on the Test
Report, Compatibility Letter, and Compatibiity List, exacty the way you entered
them. Be EXACT, as we will not process change after Program Office results
processing has completed. DO NOT USE PRODUCT CODE NAMES. ONE copy of each of
the above will be faxed. It will be up to the person receiving the reports and
letters to copy others. Note the Contact Name is the person who will get the
report and letter and that name will appear on the letter. If you are testing
and you want the Report and Letter to go to Management, then provide this name.
The following information is required

          System Manufacturer

          System Model Name

          Contact Name (Will be sent Letter and name will appear on Letter)

          Contact Phone Number

          Contact FAX Number

          Contact E-mail Address

          OS/2 Boot Partition

          OS/2 Testcase Partition

           Note:  Testkit will use partitions chosen during testkit
           installation.

          OS/2 Release Level

           Note:  Will reflect base level, i.e. 4.0. Update entry if you
           applied fix level during OS/2 install.
      Select one (1) of the following

          Create Results Diskette

          Update  Results Diskette

      If selecting 'Create Results Diskette', this selection will display a
      window where the tester is prompted for a blank diskette to begin this
      process.

      If Selecting 'Update Results Diskette', this selection displays a window
      where the tester is prompted for the original RESULTS diskette created
      when tests results were first collected.

      The collection of test results is a multiple step process and has the
      following features

          Format a scratch diskette if required

          Create sub-directories on the Test Results Diskette

          Collect or update test results from the test system

          Analyze test results

          Write TESTBAD file to Test Results Diskette, if any

          Write PCMSCORE.TXT file to Test Results Diskette

          Write PCMSCORE.TXT file to hard file (C \PCMLOGS\PCMSCORE.TXT)

          Display PCMSCORE.TXT file

      Once this process has begun, note that the system is writing test results
      ( pcmscore.txt) to the A  drive. Please wait while test results are being
      collected.

      When this process completes, all the test results have been collected,
      results have been verified. Click on Done when this process completes and
      a summary file of test results will be displayed.

      Please review the PCMSCORE.TXT display for any tests that indicate FAIL

      To exit from the summary file (PCMSCORE.TXT), select EXIT

      The PCMSCORE.TXT file can be re-displayed by typing  TYPE PCMSCORE.TXT
      from the C \PCMLOGS directory

      If a test indicates FAIL, examine the TESTBAD file on the Test Results
      Diskette (A \) which provides further detail information.  The file can
      be displayed by typing the following  TYPE A \TESTBAD.

      To rerun a test, the test can be rerun by selecting test cases from the
      PCM TEST icon on the Desktop or by referring to "Section 1-Individual
      Test Case Documentation".

      When the failing test has been re-run, begin this process again by
      clicking on the icon PCM RESULTS.


ΓòÉΓòÉΓòÉ 1.17.1. Completed Test Results ΓòÉΓòÉΓòÉ

When results are complete, please review the criteria for compatibility. All
tests in Section 1 are required to be passing for OS/2 Compatibility. In
addition, PCMCIA test will need to be successful, if the test system supports
PCMCIA devices.


ΓòÉΓòÉΓòÉ 1.17.2. Mailing Test Results Diskettes ΓòÉΓòÉΓòÉ

When all tests in Section 1 show 'PASS' in the PCMSCORE.TXT file, the Test
Results Diskette is ready to be mailed to the program office. DO NOT MAIL
FAILING TEST RESULTS. If you have given your best shot at determining the cause
of failure and still can't complete the test, call the Program Office for help.

When the Program Office receives your test resutls diskette, our validation
system will verify that all resutls passed. If results passed, the system will
generate and fax a passing test report and completion letter to the person
indicated as "Contact Name" when the test results diskette was created above.
If there are any failing tests at this point, it means that you contacted the
Program Office before sending the diskette. There have been circumstances where
a test will pass when run manually but may not when run automated. If there are
exceptions, they should be resolved before submission.


Be certain to maintain a copy of the Test Results Diskette before sending to
the program office. PLEASE DO NOT USE THE WRITE PROTECT TABS TO WRITE PROTECT
DISKETTES. When we process your results we need to write to the diskette.

The address of the Program Office to mail Test Results Diskettes, is in the
CONTACT LIST information at the beginning of this test documentation

DISKETTE LABEL

The diskette label should contain the following information  PLEASE PRINT
CLEARLY! If you have a business card, please enclose with diskette.

                     MANUFACTURER

                     MODEL NAME or NUMBER

                     TESTER (can be different from Contact Person above)

                     PHONE NUMBER

                     FAX NUMBER

                     DATE


ΓòÉΓòÉΓòÉ 1.17.3. Use of the OS/2 Approved and Ready Logo ΓòÉΓòÉΓòÉ

You must submit a signed OS/2 Approved  Ready Logo Licence Agreement before you
can use the Logo in any product promotional presentations,  product product
packaging, or product display. Please contact the Program Office for this
agreement.

Note:  The Completion Letter may be presented to show that your product is OS/2
compatible and is listed, but it is not a license to use the OS/2 Approved and
Ready Logo.


ΓòÉΓòÉΓòÉ 1.18. PROBLEM REPORTING ΓòÉΓòÉΓòÉ

Meaningful analysis, resolution, and disposition of problems is most
effectively accomplished when the problem can be replicated on a local system
where OS/2 testers and code developers can experience the problem first hand.

Problem resolution most probably will require the problem to be repeatable on a
computer system that is the same or similar to the system on which the problem
first occurred.

In the event that problem analysis fails to resolve a test failure, problem
resolution may require that test system be shipped to the IBM OS/2
Compatibility Lab for problem recreation.

When problems are encountered, please debug the problem as far as possible
prior to contacting the Program Office for support. Furthermore, it is
recommend that all the tests, or as many as possible, should be attempted prior
to reporting problems.

The support structure that is established requires the problem to be documented
in detail, on the forms identified in this section, and then FAXED to the OS/2
Compatibility Program Office. See the CONTACT list for the IBM Regional Program
Office providing support.

Problem Reporting Forms

For reporting problems, the following information is required

   1. Problem Notification (FILE  PROBLEM.TXT), located in directory C
      \OS2\PROBLEM.TXT

      This form (PROBLEM.TXT) is a sample of the type of data that is needed to
      work the problem.  Please provide this form or other form that contains
      the completed information.

   2. Test System Configuration (FILE  MACHINE.TXT), located in directory C
      \PCMLOGS)

      The Test System Configuration data is the FILE created when selecting the
      icon, PCM_HDW from the icon on the Testcase Selection  Execution window.

   3. Other LOG files as necessary.


ΓòÉΓòÉΓòÉ 1.18.1. Level 1 Support ΓòÉΓòÉΓòÉ

Level 1 support begins with problem notification. The Problem Re-creation team
receives the faxed forms that clearly characterizes the problem.


ΓòÉΓòÉΓòÉ 1.18.2. Level 2 Support ΓòÉΓòÉΓòÉ

Level 2 is problem analysis and a sizing of the effort to replicate the
problem.


ΓòÉΓòÉΓòÉ 1.18.3. Level 3 Support ΓòÉΓòÉΓòÉ

Level 3 support, if required, will be problem recreation, debug, and resolution
followed by notification.

At all levels of support, there may be the need for a member of the support
team to contact the originator of the problem for additional information.
Please be sure this information is provided on the fax sent to the Program
Office.


ΓòÉΓòÉΓòÉ 2. SECTION (1) TESTS - Individual Test Documentation ΓòÉΓòÉΓòÉ

The individual test cases in the following documentation can be used when
re-running a single test manually (i.e. after a test failure has been
corrected). These tests are run by entering the appropriate command from the
command line. Also an individual test can be re-run at any time by selecting
the test group from the PCM TEST icon on the Desktop.


ΓòÉΓòÉΓòÉ 3. Test # 1  SYSTEM HARDWARE CONFIGURATION-SNFOO1 ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 3.1. PURPOSE ΓòÉΓòÉΓòÉ

The configuration of the test system is required to be completed prior to
mailing test results to the program office.

For convenience, a hard copy of a Configuration data is included in this
documentation on the last few pages. Use these pages to collect the data prior
to data entry.  The RESULTS process will look for this data and if not created,
an error will be posted for Test # 1.

Select the icon PCM KIT then select icon PCM HDW

The panel "System Hardware Configuration" is presented. When the first screen
is complete, please click on 'Continue' to see the following two pages.

When complete, click on Save and Exit.  Once an entry is complete and changes
are necessary, click on Save and Exit and begin this process again.

The file, MACHINE.TXT, is created and saved in the SNFOO1 subdirectory for all
the system configuration data.

This is a required function of this test and the RESULTS process will look for
the file and if not created, the results process will post an error for Test#1
SNF001.


ΓòÉΓòÉΓòÉ 4. Test # 2  FILE I/O USING SEMAPHORES-SNF002 ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 4.1. PURPOSE ΓòÉΓòÉΓòÉ

Test for semaphores, video I/O, file I/O,  inter-process communications. Also
included are additional tests for semaphores that are output from the Kernel
test.


ΓòÉΓòÉΓòÉ 4.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 Full Screen command prompt, change to the D  drive and type
      CD BATCH and press ENTER

   2. Type  SNF002  and press ENTER compac.

          SNF002 will execute and complete in about five (5) minutes.

          At test end you are returned to D \BATCH directory proceed to check
           results.

 Results

 At test end a message will be displayed as follows

     --------------------------------------------------------

     Scanning output log \ACCEPT\CORE\SNF002.LOG for "PASS"

     --------------------------------------------------------

     There should be 59 entries

     D \ACCEPT\CORE\SNF002.LOG  59

     At end, you are returned to the test drive prompt.

 If the SNF002.LOG file does not show 59 occurrences, then view the log to see
 which files did not pass.

   1. When any file shows 'FAIL', then you are asked to re-run the test from
      the beginning.

          Restart the system before rerunning this test by selecting Shutdown
           on the Toolbar.

 Error Files

 As above

 Run Time

 Approximately  5 minutes.


ΓòÉΓòÉΓòÉ 5. Test # 3  COLLATING SEQUENCE  CASE MAPPING TEST ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 5.1. PURPOSE ΓòÉΓòÉΓòÉ

Test for the National Language Standard (NLS) Collating Sequences and Case
Mapping Tables.  Files are generated and compared to a current list. Output
files are written for the user to verify before submitting results.  Test will
run both DOS  OS/2 commands.


ΓòÉΓòÉΓòÉ 5.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 Full Screen prompt, in the D  drive, type CD BATCH

   2. TYPE SNF005 and press ENTER compac.

          The test will run to completion.
 Results

 At the end of the test, the test results from the DOS version (REAL.RES) will
 be displayed on the screen.

 compac.

     To see the test results from the OS/2 version, type TYPE C
      \NLSDOC\PROT_RES

     To see the test results form the DOS version, type TYPE C \REAL_RES

 Both files should have the message 'THE FILES COMPARE OK'.

 Note:  If the above message does not display, display the file and observe the
 failing calls at the bottom of the file.  There should be only one failing
 call to CODE '666', COUNTY 'NOWHERE'.

 The output files are in the D \NLSDOS directory. compac.

     Type TYPE OS2DATA.PRI and scroll to bottom of file

     Type TYPE OS2DATA.SEC and scroll to bottom of file

     Type TYPE DOSDATA.PRI and scroll to bottom of file

     Type TYPE DOSDATA.SEC and scroll to bottom of file

 If there is more than one failing call, then the test did not complete
 successfully.  Restart the test system and run the test again.

 Error Files

 None

 Run Time

 Approximately 3 minutes


ΓòÉΓòÉΓòÉ 6. Test # 4  CODE PAGE SWITCHING (VIDEO/PRINTER)-SNF006 ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 6.1. PURPOSE ΓòÉΓòÉΓòÉ

Comprehensive test of objects that are within folders, and the display of ASCII
codes with a range of different background colors.

A printer should be selected; check the DESKTOP for the printer icon.


ΓòÉΓòÉΓòÉ 6.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 Full Screen prompt, in the D Drive, type CD\BATCH

   2. Type SNF006 at the command prompt

   3. Test case will switch sessions and present a screen of all the ASCII
      characters and will begin to change colors

   4. The system will beep if there are errors (wrong keyboard information) and
      will take less than 5 minutes to complete

   5. When the test is finished, and you are returned to D \BATCH sub
      directory,

 Note:  If this test is run in SVGA mode, the file, CPALOG, will show 39 lines
 of Font_Demon found wrong code page, and will end with CPALOG FAILED.  This is
 a successful run for SVGA.

 Results

 Verify the test results, at the command prompt D \NLSCPA, type the following
 compac.

   1. Type TYPE FONTD and press ENTER

   2. Type TYPE PRINTD and press ENTER

   3. Type TYPE CPALOG and press ENTER

   4. Type TYPE SWITCH_6 and press ENTER

 Each file will be displayed and at the end will be 'PASS' or 'SUCCESSFUL', or
 'FAIL'.

 Run Time

 Approximately 5 minutes.


ΓòÉΓòÉΓòÉ 7. Test # 5  SHARED SEGMENTS TEST-SNF007 ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 7.1. PURPOSE ΓòÉΓòÉΓòÉ

Multiple memory allocation calls


ΓòÉΓòÉΓòÉ 7.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 Full Screen prompt, in the D  Drive, type CD\BATCH and press
      ENTER

   2. Type SNF007 and press ENTER compac.

          The test will run for less than 10 MINUTES compac.

          At test end, you are returned to a OS/2 Full Screen Prompt.
 Results

 At test end, in the D \LOGA directory, the file SWITCH_7 will be displayed
 indicating 'PASS' OR 'FAIL'  information for  compac.


     M32SHR

     NAMESHR

     GIVESHR

     GETSHR

 Error File

 This test will produce one (1) file.  This file is not an error file unless
 the data in the file indicates a failure. The file is in D \LOGA directory as
 listed above.

 Run time

 Approximately 10 minutes.


ΓòÉΓòÉΓòÉ 8. Test # 6  HIGH PERFORMANCE FILE SYSTEM TEST-SFFBPB ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 8.1. PURPOSE. ΓòÉΓòÉΓòÉ

Testing the HPFS file system. compac.

Note:  Verify there are no disk errors prior to test execution by using "CHKDSK
C  /F 3" for each HPFS partition prior to running test. Test may hang
otherwise.


ΓòÉΓòÉΓòÉ 8.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 Full Screen prompt, in the D  Drive, type  CD BATCH  and
      press ENTER

   2. Type SNFBPB at the command prompt and press ENTER

      Note:  The command SNFBPB.CMD looks at C , D , E  and F  for the first
      HPFS partition it finds. If all these partitions are FAT, the test will
      end and OS/2 will return to the D \BATCH sub directory.

   3. If an HPFS partition is found, verify that the directory displays long
      file names as HPFS allows file names up to 256 characters

   4. Test will end and return to an OS/2 Full Screen command prompt.

 Results

     THE log file \BATCH\SNFBPB_L will indicate PASS or FAIL

     Or 'NO HPFS' found.

 Error Files

 As above.

 Run Time

 Approximately 5 minutes.


ΓòÉΓòÉΓòÉ 9. Test # 7 BATCH PROCESSING AND REXX CALLS-SNFREXX ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 9.1. PURPOSE ΓòÉΓòÉΓòÉ

To verify the REXX language with OS/2.


ΓòÉΓòÉΓòÉ 9.2. Test Process ΓòÉΓòÉΓòÉ

   1. At the OS/2 Full Screen prompt, in the D  Drive, type  CD BATCH and press
      ENTER

   2. Type  SNFREXX  at the command prompt There will be two (2) commands that
      display  sys errors, (SYS 1041)  as these commands are designed to fail

   3. At test completion time, you will be returned to an OS/2 Full Screen
      prompt.
 Results

     At test end, a message will be displayed  scanning output log REXX_LOG
      for "OK"

     Display will show D \rexx\rexx_log  71

 If there are not 71 entries, type TYPE REXX_LOG |MORE and visually inspect
 each command line for "BAD".

 Error Files

 None.

 Run Time

 Approximately 3 minutes.


ΓòÉΓòÉΓòÉ 9.3. Results ΓòÉΓòÉΓòÉ

Create the file REXX_LOG in the REXX directory


ΓòÉΓòÉΓòÉ 10. Test # 8  AUTOMATED BASE SYSTEM STREST TEST-SNFMVDM ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 10.1. PURPOSE ΓòÉΓòÉΓòÉ

Collection of small tests that will require a mouse and a printer to be
attached to your system.


ΓòÉΓòÉΓòÉ 10.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. At an OS/2 Full Screen prompt, in the D  drive, type CD BATCH

   2. Type SNFMVDMand let the test run by itself until Logical Screen Group 1
      is visible on desktop with flashing colors  character boxes

      Note:  The box with the flashing colors will appear once on the Desktop,
      then go away momentarily, and appear again.  This may happen rather
      quickly, depending upon the speed of the machine.
 compac.

     After the second window of flashing colors appears for a full five (5)
      minutes, end the video part of this test by pressing Q.

     The test will end, the window will close and you will be returned to the
      OS/2 Full Screen prompt.

      Note:  Printer POP-UP window may require to 'RETRY' or 'CANCEL' to
      continue if no printer is attached, select CANCEL

     The printer will start to print several pages, or a message may be
      displayed, PRINTER NOT ON LINE, or THE LPT1 DEVICE CANNOT BE FOUND
 Results  At test end, a message will be displayed, Checking output logs under
 \VDM for "PASS"  followed by a second line There should be 7 files with PASS

   1. SWITCH_V

   2. VDM1

   3. VDM2

      Note:  Partial is OK

   4. VVTATXM4

   5. FLT018

   6. MAT015

   7. CTTCLOCK

 Error Files

 As listed above.

 Run Time

 Approximately 15 minutes.


ΓòÉΓòÉΓòÉ 11. Test # 9 YOUR DOS WINDOWS** APPLICATIONS TEST-SNFWIN ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 11.1. PURPOSE ΓòÉΓòÉΓòÉ

Test your WINDOWS** applications.

To be able to run this test, you must first load your WINDOWS** applications to
the D \WINDOW directory.

WINDOWS** applications have not been provided with this software.  You must
provide your own off the shelf DOS applications.


ΓòÉΓòÉΓòÉ 11.2. Test Process ΓòÉΓòÉΓòÉ

There are two ways to get a WINDOWS** environment.  One way is to select
WIN-OS/2 Full Screen in the OS/2 SYSTEM icon, Command Prompts folder, and the
other is to enter 'WINOS2' from a OS/2 Full Screen.  Either method will result
in a WINDOWS** 'Program Manager' screen. compac.

   1. Using a mouse, click on FILE in the action bar of the WINDOWS** PROGRAM
      MANAGER SCREEN.

   2. A pull down menu will be presented where you can select RUN.  If you
      select EXIT from this window, you will return to the OS/2 Full Screen.

   3. A RUN window will be presented where you can type in the name of the
      WINDOWS** program to RUN.

   4. CTRL-ESC will take you to the Task List Window where you can select the
      desktop

 Results

 No errors should be encountered while running your Windows** applications

 Run Time

 Depends upon your applications.


ΓòÉΓòÉΓòÉ 11.3. Test Results ΓòÉΓòÉΓòÉ

Since this test is visually verified by the test engineer, no specific output
files were generated.

If no errors were encountered, this test is complete.  Go to the next test.

If errors were encountered, create an error file, in C \PCMLOG\SNFWIN.TXT and
record the error iformation.

Do not create SNFWIN.TXT if errors are not encountered











ΓòÉΓòÉΓòÉ 12. Test # 10 STRESS TEST-PCMMED01 ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 12.1. Purpose ΓòÉΓòÉΓòÉ

This tests will collectively test the major functions of the OS/2 Operating
System in an environment that introduces an element of demand by dynamically
starting and ending tests while other tests are permitted to execute over a
period of time.

The STRESS tests were loaded before you started testing. If the STRESS tests
were not loaded at that time, you will need to go will need to go back to
LOADING THE TEST CASES documentation and load STRESS test case now.


ΓòÉΓòÉΓòÉ 12.1.1. Stress Test Execution ΓòÉΓòÉΓòÉ

This test will execute for about 4 TO 5 hours.

Note:  The test system MUST be shutdown using the Toolbar and restarted prior
to running this test.

After restarting, the PCM_TEST Full Screen is displayed.

Use ALT-ESC to go back to the Desktop to let the system open completely before
going to the PCM_TEST session to start test cases.  This should be done every
time the system is restarted.

Also, once the test starts, the test systems should be left alone until the
test completes,  These tests may fail if there is any other activity on the
system while these tests are running or if the system has not been shut down
and restarted prior to this test.


ΓòÉΓòÉΓòÉ 12.2. Test Process ΓòÉΓòÉΓòÉ

compac.

   1. The test system MUST be shutdown using the Toolbar and restarted.

   2. At the OS/2 Full Screen command prompt, change to the D \LOG directory.
      Type  RUN and press ENTER compac.

          'PCMMED01' is the default test script to run

      Note:  After a few moments, the screen will clear and you will see a
      display of three (3) bars.

   3. Insert a scratch diskette and press ANY KEY TO CONTINUE

      Note:  CTRL-C will terminate the test here if you do not want to
      continue. compac.

          Once the stress test is running, there will be numerous parallel
           processes executing at the same time.

   4. At test completion you are returned to an OS/2 Full Screen prompt, or to
      the Desktop.


ΓòÉΓòÉΓòÉ 12.2.1. Results Analysis ΓòÉΓòÉΓòÉ

The PCMMED01 test will complete in approximately 4 to 5 hours. Errors
encountered that prevent test completion as well as errors reported in the
summary file could indicate test failure.

At completion time, if the screen is at the desktop, select, with the mouse, an
OS/2 Full Screen window and at the D \LOG directory, compac.

     TYPE TYPE PCMMED01.SUM and press ENTER

 A successful execution of this stress test, the last line of the summary file
 (PCMMED01.SUM) should reflect the following

  ┤БББББББББББББББББББСБББББББББББББББББББСБББББББББББББББББББСББББББББББББББББББЖ
  В PCMMED01          В PASS 68           В FAIL  0           В PARTIAL 0        В
  ╙БББББББББББББББББББТБББББББББББББББББББТБББББББББББББББББББТББББББББББББББББББЙ
  В MISSING 0         В                   В                   В                  В
  БББББББББББББББББББ╔БББББББББББББББББББ╔БББББББББББББББББББ╔ББББББББББББББББББД

 Is some cases the file DSWITCHM will report a <PARTIAL>.  If this happens, it
 is acceptable and your passing count will be one (1) less. This <PARTIAL> is
 caused by the test case being stopped prior to completion, by the switcher
 script.

 Note:  If you do not achieve the above desired test results, you may do one or
 more of the following

   1. Make certain the test system does not have any other activity while the
      STRESS test is running

   2. Go back to step one (1) of this Test Process

   3. Reload the STRESS TESTS and begin at step one (1) of this Test Process

   4. Refer to the file, TESTHELP.KIT README on the CD-ROM for help in solving
      individual file failures, or refer to the data in this document on the
      bulletin board information.

 Note:  If partials detected other than DSWITCHM, rerun the individual testcase
 .exe with the same parms as used in PCMMED01. Then run STRLOG.CMD to update
 the summary file.


ΓòÉΓòÉΓòÉ 13. Test # 11 KEYBOARD DEVICE DRIVER TEST-KBD ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 13.1. Purpose ΓòÉΓòÉΓòÉ

Exercise the keyboard device driver.


ΓòÉΓòÉΓòÉ 13.2. Test Process ΓòÉΓòÉΓòÉ

The following test steps will require you to hit ENTER several times to allow
the test to continue.

Note:  Important! Be certain to use the ENTER key that is near the SHIFT key.
Do not use the ENTER key that is near the numeric key pad.  Allow at least 5
seconds between prompts, or a test variation may fail.  Select Shut down using
the LaunchPad and restart the system.

KBD-OS/2 Window Test

   1. Remember, do not enter the key strokes until prompted.  Hitting the key
      early may cause the variation to fail. Wait 5 seconds after prompts
      before hitting enter.

   2. From an OS/2 Window command prompt, change to the KBD directory on D
      Drive

   3. At the command prompt enter VIO -L9 (Lower case only)

      Note:  Make certain the scroll bar is down at the bottom of the window,
      in order to see the 'PRESS ENTER' message.

   4. Follow the instructions on the display as you will need to press ENTER
      several times to respond to questions about your keyboard.

      Important!

      Please do not press ENTER until prompted or the test will fail.

   5. At test completion, you are returned to D \KBD Directory

      Full Screen Protect Mode Test

   6. Open an OS/2 Full Screen session through the Desktop

   7. Change to the KBD directory on the D  Drive

   8. At the command prompt enter  DOALL -L9 (Lower case only) and press ENTER

   9. Follow the instruction on the display as you will need to press ENTER
      several times to continue the test until you are returned to the D \KBD
      Directory.

 RESULTS

 Log files are in the D \KBD directory. compac.

   1. KBDV.LOG - name of the log file created by VIO CMD

   2. KBDP.LOG - name of the log file created by DOALL CMD
 compac.

     Type  GREP "STATUS" KBDV.LOG and match the display with the following
      test results information

     STATUS .... RUN 12....PASS 12...FAIL 0...AUTOFAIL 0

     STATUS .... RUN  2....PASS  2...FAIL 0...AUTOFAIL 0
 compac.

     Type  GREP "STATUS" KBDP.LOG and match the display with the following
      test results information.

     STATUS .... RUN 12....PASS 12...FAIL 0...AUTOFAIL 0

     STATUS .... RUN  2....PASS  2...FAIL 0...AUTOFAIL 0


ΓòÉΓòÉΓòÉ 13.2.1. Log File Output ΓòÉΓòÉΓòÉ

compac.

     File KDBV.BAK contains output for last execution of DOALL.CMD.

     File KDBP.BAK contains output for last execution of VIO.CMD


ΓòÉΓòÉΓòÉ 13.2.2. KBD Directory Contents ΓòÉΓòÉΓòÉ

headh0

 COMPONENT     IOCTL INTERFACE

 DOALL.CMD     Full Screen Protect Mode test.

 VIO.CMD       runs the OS/2 window test.

 11KBD14.EXE   12 variations.

 11KBD14A.EXE  11KBD14.EXE.

 11KBD14B.EXE  11KBD14.EXE.

 11KBD14C.EXE  11KBD14.EXE.

 11KBD15.EXE   2 variations.

 11KBD16.EXE   6 variations.

 11KBD18.EXE   codepage support

               2 variations

 Logging Levels  (-L#)(Lower Case Only)

 The logging level switch provides a method for logging error messages from the
 test cases into a log file. There are 7 logging levels. Each level logs
 messages for that level and all levels below  compac.

     Level 1  Logs program description or header.

     Level 2  Logs abort messages.

     Level 4  Logs fail messages. *Default

     Level 6  Logs warning messages.

     Level 7  Logs trace messages.

     Level 8  Logs low-level trace messages.

     Level 9  Logs debug messages.
 It is recommended that logging level 9 be used for the keyboard test.

 Run Time

 The total run time for the KBD bucket is approximately 15 minutes.


ΓòÉΓòÉΓòÉ 14. Test # 12 DISK MULTI-TASKING TEST-FVTDISK ΓòÉΓòÉΓòÉ

Purpose Exercise the file systems use of Drive D


ΓòÉΓòÉΓòÉ 14.1. Test Process ΓòÉΓòÉΓòÉ

From an OS/2 Full Screen command prompt, change directory to At D \CMD
directory, type FVTDISK and press ENTER

Note:

   1. All the parameters for FVTDISK are in FVTDISK.CMD

   2. The defaults for FVTDISK are logical drive C  when running FVT from the
      PCM_TEST icon. These are changed automatically to the values entered on
      the menu.

 RESULTS

 FVTDISK will create a log files named D \LOGF\DASDSTD1.LOG and D
 \LOGF\DASDSTD2.LOG

 Run Time

 Approximately 15 minutes.


ΓòÉΓòÉΓòÉ 15. Test # 13 FORMAT UTILITY TEST-FORMAT ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 15.1. Purpose ΓòÉΓòÉΓòÉ

Verify the FORMAT function for various diskette media.

NOTE! This test program has the potential of testing 5.25 and 3.50 diskette
sizes. However, since your system may not contain both variations, test only
the media resident in the system.

Prior to running the test, Select Shut down using the Toolbar and restart the
system.

The FORMAT utility testcase files are setup to execute both the OS/2 .CMD
testcases and the DOS .BAT testcases.  The output  LOG files are scanned using
GREP.EXE to look for the STATUS lines to provide summary PASS/FAIL status.


ΓòÉΓòÉΓòÉ 15.2. Test Process ΓòÉΓòÉΓòÉ

An assumption has been made that the 1.44 MB or the 1.2 MB drive is drive A. If
your configuration is different, you will need to edit the .INP file and change
the drive letter on both the command line and FTEST line of the input files.
compac.

   1. Open an OS/2 full Screen Session (Change to the PCM_TEST if active)

   2. Place a scratch diskette in the A  Drive

      Note:  If Drive A  is 1.44 MB Diskette Drive then do  compac.

          Type CD \FORMAT and press ENTER

          Type  TST1_44.CMD  and press ENTER


ΓòÉΓòÉΓòÉ 15.2.1. Format directory Contents ΓòÉΓòÉΓòÉ

FORMAT (sub directory) headh0

 COMPONENT           DESCRIPTION

 FMT1_44.CMD         Batch file used to run the OS/2 Full Screen test for 1.44
                     MB diskette drive and media.


ΓòÉΓòÉΓòÉ 15.2.1.1. Results Logging ΓòÉΓòÉΓòÉ

At the end of each .LOG file, a summary status is presented showing the number
of variations run, variations pass and variations fail.

Change to the D \LOGF Directory compac.

     TYPE FLOP144.LOG or FLOP525.LOG

     TYPE DSKTRSLT.LOG
 Run Time

 Approximately 20 minutes per drive media.


ΓòÉΓòÉΓòÉ 16. Test # 14 TIMER DEVICE DRIVER TEST-TIMERDD ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 16.1. Purpose ΓòÉΓòÉΓòÉ

Two (2) tests, they are

DH test calls functions provided in the TIMEX1.SYS to test DevHlp_SetTimer,
DevHlp_ResetTimer, and DevHlp_TickCount at task and interrupt time.  This test
contains 18 variations.

HZ32 test will verify that the interrupt rate from channel 8 (from the Intel
8254 Interrupt chip) occurs at a rate of 31.25 Hz.  This test contains one (1)
variation.

Note:  There is a README file in the TIMERDD directory on the test diskette.
More information is available about this test in this file.

 IMPORTANT!
 If your test system is connected to a network, some tests may not be
 successful.  For example, you may notice some timer handlers between
 18 through 25 are not set.
 This is acceptable.  There can be up to ten (10) timer handlers
  that may not be set and not affect OS/2 compatibility.
 However, if you have more than ten (10) timer handlers not set, it
 may be necessary to shut down the other processes and re-run the
 test.


ΓòÉΓòÉΓòÉ 16.2. Test Process ΓòÉΓòÉΓòÉ

   1. Type CD TIMERDD

   2. Type TIMER

      Note:  The TIMER.CMD will run both tests.

   3. Control is returned to Full Screen prompt in the D \TIMERDD directory

 Test Results

 DH TESTS results are stored in the TIMERDD directory

 In the TIMERDD\DH\DH directory, you will find the file DH.LOG

 Type  TYPE DH.LOG |MORE  and press ENTER.

 Note:  This file will contain the results of the DH test.  Each variation will
 need to be looked at to determine success or failure.  There are 18
 variations.  They will not run consecutively.

 HZ32 Test

 In the TIMERDD\IRQ8 directory, you will find the file HZ32.LOG

 Type TYPE HZ32.LOG |MORE and press ENTER.

 Note:  This file will contain the results of the HZ32 test.  At the end of the
 file, the test variation will show SUCCESS or FAIL.

  TIMERDD Directory Contents

 TIMERDD (sub directory)

 compac.

     \TIMERDD\DH\DH\DH.EXE

     \TIMERDD\DH\TIMEX1\TIMEX1.SYS

     \TIMERDD\IRQ8\HZ32\HZ32.EXE
 Run Time

 Approximately 50 minutes for the DH.EXE test.

 Approximately 1 minute or less, for the HZ32.EXE test.


ΓòÉΓòÉΓòÉ 17. Test # 15 PRINTER DEVICE DRIVER TEST-PRINTDD ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 17.1. PURPOSE ΓòÉΓòÉΓòÉ

Test for printer device drivers to the parallel ports on your system.  These
ports are know as LPT1, LPT2 or LPT3.  These ports can be tested individually
or collectively.


ΓòÉΓòÉΓòÉ 17.2. Test Process ΓòÉΓòÉΓòÉ

Connect a printer to the LPT port(s) you want to test.

OS/2 FULL SCREEN PRINTER TESTING

   1. Open a OS/2 Full Screen session.

   2. Change to the PRINTDD directory on the D  drive

          To test LPT1 only, type PRINT1 and press ENTER

          To test LPT2 only, type PRINT2 and press ENTER

          To test LPT3 only, type PRINT3 and press ENTER

          To test LPT1  LPT2, type PRINT1 2 and press ENTER

          To test LPT1  LPT3, type PRINT1 3 and press ENTER

          To test LPT2  LPT3, type PRINT2 3 and press ENTER

          To test LPT1, LPT2  LPT3, type PRINTALL and press ENTER

   3. At test end, control is returned to OS/2 Full Screen

 DOS PRINTER TESTING

   1. Open a DOS Full Screen session.

   2. Change to the PRINTDD directory on the D  drive

          To test LPT1 only, type PRINT1 and press ENTER

          To test LPT2 only, type PRINT2 and press ENTER

          To test LPT3 only, type PRINT3 and press ENTER

          To test LPT1  LPT2, type PRINT1 2 and press ENTER

          To test LPT1  LPT3, type PRINT1 3 and press ENTER

          To test LPT2  LPT3, type PRINT2 3 and press ENTER

          To test LPT1, LPT2  LPT3, type PRINTALL and press ENTER

   3. At test end, CTRL-ESC to the Task List Window and click on waiting DOS
      PRINT test.

   4. All tests are done when the DOS test is completed.

 LOGGING OS/2 PRINT TEST RESULTS

 Note:  To view output as successful, for example  Type  TYPE PRT1OS.LOG and a
 message will be displayed 'PASSED IF ALL CHARACTERS WERE PRINTED.

     PRT1OS.LOG  - Logs PRINT1.CMD results

     PRT2OS.LOG  - Logs PRINT2.CMD results

     PRT3OS.LOG  - Logs PRINT3.CMD results

     PRT12OS.LOG  - Logs PRINT1 2.CMD results

     PRT13OS.LOG  - Logs PRINT1 3.CMD results

     PRT23OS.LOG  - Logs PRINT2 3.CMD results

     PRTALLOS.LOG - Logs PRINTALL.CMD results
 LOGGING DOS PRINT TEST RESULTS

 Note:  To view output as successful, for example  Type  TYPE PRT1DOS.LOG and a
 message will be displayed 'PASSED IF ALL CHARACTERS WERE PRINTED.

     PRT1DOS.LOG  - Logs PRINT1.BAT results

     PRT2DOS.LOG  - Logs PRINT2.BAT results

     PRT3DOS.LOG  - Logs PRINT3.BAT results

     PRT12DOS.LOG  - Logs PRINT1 2.BAT results

     PRT13DOS.LOG  - Logs PRINT1 3.BAT results

     PRT23DOS.LOG  - Logs PRINT2 3.BAT results

     PRTALDOS.LOG  - Logs PRINTALL.BAT results.

 Run Time

 Approximately 10 minutes


ΓòÉΓòÉΓòÉ 18. Test # 16  OS/2 MULTIMEDIA TEST ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 18.1. Purpose ΓòÉΓòÉΓòÉ

Verify proper functionality of various Multimedia Presentation Manager/2
(MMPM/2) components.  These components provide a minimal representative test
for multimedia usability in which they exercise the wave audio, MIDI, CD and
digital video devices.


ΓòÉΓòÉΓòÉ 18.2. Multimedia Requirements ΓòÉΓòÉΓòÉ

This test is required if the test system is shipped with either SOUND support
and/or a CD-ROM.

Since the Multimedia test cases must be loaded from the OS/2 Compatibility Test
Kit CD-ROM, see chapter on LOADING TEST CASES, if the test system is not
shipped with a CD-ROM, the test system must be configured for a CD-ROM. We
suggest connecting an external CD-ROM using the parallel port to load the
Multimedia test cases.


ΓòÉΓòÉΓòÉ 18.2.1. Automatic Test Selection and Execution ΓòÉΓòÉΓòÉ

The Multimedia tests will run unattended by selecting the test cases from the
Selection  Execution screen.

Note:  To run the Multimedia tests manually from the command line, see the
'Manual Test Execution' which follows the automatic description.

If the test system has sound support

     If Testkit drive is HPFS, you must run PCM_HPFS.

     IF your video is VGA, you must run PCM_VGA.

     IF your video is SVGA, you must run PCM_SVGA.

     You must run PCM_FLC.

     You must run PCM_REXX.

      The next test selections will require a music CD in the CD-ROM drive.

     If the test system has a CD-ROM, you must run PCM_CD

     If the test system has sound support and a CD-ROM that supports
      streaming, then you must run PCM_CDS.

     When all tests have been selected, then click on RUN


ΓòÉΓòÉΓòÉ 18.2.2. Manual Multimedia Test Case Execution ΓòÉΓòÉΓòÉ

Before running these tests, change directory to  CD\BUILD\SRC\SVT\BUCKCMD

If the test system has sound support and

     The test drive is HPFS, then run PCM_HPFS.CMD and press ENTER

     Your video is VGA, then type RUNMME PCM_VGA and press ENTER

     Your video is SVGA, then type RUNMME PCM_SVGA and press ENTER

     Type RUNMME PCM_FLC and press ENTER

     Run PCM_REXX.CMD and press ENTER

      The next test selections will require a music CD in the CD-ROM drive.

     If the test system has a CD-ROM, then type RUNMME PCM_CD an press ENTER

     If the test system has sound support and a CD-ROM that supports
      streaming, then type RUNMMP PCM_CDST and press ENTER

     As each test ends, the script file will finish and return to an OS/2 Full
      Screen prompt
 RUN TIME

 Test Duration is about 30 minutes for each test.


ΓòÉΓòÉΓòÉ 18.3. Test Results ΓòÉΓòÉΓòÉ

The log files are located in directory D \RESULTS\MMEPCM\SVTLOG

The test results are in directory D \RESULTS\MMEPCM\SVTRAW\ and are collected
automatically, see COLLECTING TEST RESULTS. Log files are in Directory
\RESULTS\MMEPCM\SVTLOG\ and have the same name as the output files but end with
the .LOG  extension.

     The file  PCM_SVGA.RA_  contains the SVGA results

     The file  PCM_VGA.RA_  contains the VGA results

     The file  PCM_HPFS.RA_  contains the HPFS results

     The file  PCM_CD.RA_   contains the CD Music results

     The file  PCM_CDS.RA_  contains the CDS Music results

     The file  PCM_FLC.RA_  contains the FLC results

     The file  REXXRSP.OUT  contains the PMREXX results

 Note:  There will be a total of

     11 TESTS for VGA systems

     12 TESTS for SVGA systems

     1 TESTS for HPFS system

     2 TESTS FOR FLC

     7 TESTS for CD MUSIC

     6 TESTS for CDS MUSIC

 Note:  If this test is run more than once, the output files will be appended
 with the new test results. To prevent this file from getting very large, run
 the command, 'RESETLOG' from the D \UTIL directory. This .CMD file will delete
 all files generated by this test.

 This is the end of the Section 1 tests. If test results have not been
 collected, refer to the chapter on "COLLECTING TEST RESULTS" now.


ΓòÉΓòÉΓòÉ 19. SECTION (2) TESTS - Individual Test Documentation ΓòÉΓòÉΓòÉ

This section of the test kit contains additional tests that may be required for
OS/2 Compatibility.  These additional components are

     APM

     PCMCIA

     SMP

     SPEECH
 If the system that is being tested will be marketed with one or more of the
 above components, then you are required to run the specific test.  Please read
 the test case purpose at the beginning of each test case to determine test
 requirements.


ΓòÉΓòÉΓòÉ 20. Test # 17 ADVANCED POWER MANAGEMENT TEST-APM ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 20.1. Advanced Power Management (APM) Chapter Overview ΓòÉΓòÉΓòÉ

The OS/2 Advanced Power Management (APM) feature provides support for an
industry standard developed jointly by Intel and Microsoft to conserve battery
power in certain classes of computer systems. APM covers every aspect of AC/DC
power consumption/utilization for these personal computer systems. This is
accomplished through using a BIOS file unique to the specific hardware and
providing a user interface to it. The details of this OS/2 interface are
provided in DCR 26087 and several related Workbooks.

The set of tests in this chapter are designed for BOTH the APM hardware related
tests plus aspects of the PM user interface through the Power object installed
in the OS/2 System Setup folder.


ΓòÉΓòÉΓòÉ 20.1.1. Objectives ΓòÉΓòÉΓòÉ

The purpose of this set of tests is to ensure that the OS/2 Advanced Power
Management (APM) function performs, from a Workplace Shell System Test
perspective, to the requirements as defined in DCR 26087 and the related APM
Workbooks.

There are two major hardware classifications to be considered. First are those
systems (IBM and OEM) which provide hardware support for the APM function.
These are typically laptop, palmtop, pen and other systems which may be battery
powered. Secondly are those systems which do not provide APM hardware support.


ΓòÉΓòÉΓòÉ 20.2. Advanced Power Management Test Scenario Overview. ΓòÉΓòÉΓòÉ

   1. Power state definitions
   2. Advanced Power Management Test.
          APM installed correctly and power object found.

          Power object shows correct status for battery or A/C power and
           battery life remaining.

          Standby and Suspend/Resume modes work correctly.

          Power object refreh functions work correctly.
   3. Forms for reporting test results



ΓòÉΓòÉΓòÉ 20.2.1. Non APM supporting hardware ΓòÉΓòÉΓòÉ

If a Selective Install is done to "force" APM installation on a system and the
Power object is opened, the following message may occur  "The system cannot
load the APM feature". This can be caused by your system not supporting this
feature or because the APM device driver was not installed.


ΓòÉΓòÉΓòÉ 20.2.2. Power state definitions ΓòÉΓòÉΓòÉ

There are a set of four power states supported by the APM 1.0 Specification

      READY (0000h) - Indicates that the system or device is operating at full
      power.

      STANDBY (0001h) - Indicates that the system or device is operating at
      partial power which allows for IMPROVED energy conservation without
      noticeable power-up delays for re-establishing operation. System will
      respond to interrupts such as pressed keyboard keys. Either an interrupt
      or Restore button re-establishes power.

      SUSPEND (0002h) - Indicates that the system or device is operating at
      partial power which allows for SUBSTANTIAL energy conservation with
      accepted noticeable power-up delays for re-establishing operation. All
      interrupts and power usage except system memory is disabled. Only the
      Restore button re-establishes power. The APM 1.0 BIOS Spec defines this
      as a system wide state and does not currently support a device specific
      state although the OS/2 architecture allows both.

      OFF (0003h) - Indicates that the system or device is not operating or
      receiving any amount of power.

      Note:  Going from SUSPEND state to OFF state IS NOT supported in the
      current implementation of OS/2 APM. To power off from Suspend, first
      Resume the system and then do a Shutdown as normal prior to power off.


ΓòÉΓòÉΓòÉ 20.2.3. Advanced Power Management (APM) Test ΓòÉΓòÉΓòÉ

The following set of APM test steps describes a brief test of the APM functions
installled on a system with the OS/2 Operating System.

   1. Make sure the battery is fully charged.
   2. Set hardware timers for screen blanking to 3-5 minutes and suspend timer
      to 15min or more.
   3. Verify the following are present in CONFIG.SYS

      Ver 3.0
          DEVICE=C \OS2\APM.SYS

          DEVICE=C \OS2\MDOS\VAPM.SYS

      Ver 4.0
          DEVICE=C \OS2\BOOT\APM.SYS

          DEVICE=C \OS2\MDOS\VAPM.SYS
   4. Verify that Power Object is in System Setup folder.
   5. Open an OS/2 window session and insert a scratch diskette in drive A ,
      then start D \CMD\DRAIN.CMD
   6. Open the OS/2 System Setup folder and double click on the Power Obj ect.
   7. Verify that the system shows "AC Powered" and "Battery State High"
   8. Unplug A/C Charger.
   9. Click on system menu for Power Object and select "Refresh Now".
  10. Verify that system shows "Battery Powered" and "Battery State High" .
  11. Allow the system time to enter standby mode (screen blanks).
  12. Touch key(s) to bring system out of standby mode, and verify that
      drain.cmd is still running (let it run a couple minutes).
  13. Click on system menu for Power Object and select "Suspend", answer "Yes"
      on pop-up menu to continue suspend operation.
  14. Touch key(s) to bring system out of suspend mode, verify that the desktop
      is ok, and that the drain.cmd continues running.
  15. Click on system menu for Power Object and select "Refresh" to bring up
      the sub-menu, and select "On" to setup automatic refresh.
  16. Open Power Object settings/properties, on the View Tab, set refresh on,
      and refresh rate to 1-2 minutes.
  17. Let the system run for 30 minutes, verify that the battery life bar shows
      an indication of battery drain.
  18. Plug in A/C charger, wait for automatic refresh to occur (1-2 minut es)
      and verify that Power Object now shows "AC powered".
  19. Stop drain.cmd in OS/2 window with CTRL-BREAK.
  20. Let battery charge for 30 minutes or more.
  21. Verify that Power Object battery life indicates increased charge.
  22. Close Power Object.


ΓòÉΓòÉΓòÉ 20.3. Test Results - FULL APM TESTING ΓòÉΓòÉΓòÉ

Since this test is visually verified by the test engineer, no specific output
files were generated.  To obtain OS/2 Compatibility for Advanced Power
Management, complete the information in the file 'APM.TXT which is in the APM
sub directory on the Test Results Diskette.  A copy of the form is on the next
page.


ΓòÉΓòÉΓòÉ 21. Test # 17 APM TEST RESULTS WORKSHEET ΓòÉΓòÉΓòÉ

                    PCM COMPATIBILITY TESTKIT

            ADVANCED POWER MANAGEMENT - TESTS RESULTS



Inidate the status for each of the test scenarios with an "X" in the
appropriate column.

Power State Definitions - READY..........................  PASS__FAIL__

                        - STANDBY........................  PASS__FAIL__

                        - SUSPEND........................  PASS__FAIL__

                        - OFF............................  PASS__FAIL__



OS/2 APM installed correctly and power object found......  PASS__FAIL__
   Comments



Power Object shows A/C powered when A/C charger connected. PASS__FAIL__
   Comments



Power Object shows Battery powered and battery life when   PASS__FAIL__
A/C charger is disconnected when refresh now chosen.
   Comments



System enters/exits standby mode (screen blank) correctly  PASS__FAIL__
   Comments



System enters/exits suspend mode correctly, and drain.cmd  PASS__FAIL__
was resumed running on return from suspend mode.
   Comments



Power Object refresh now and automatic refresh shows       PASS__FAIL__
changes in battery/power states.
   Comments




Copied to Test Results Diskette - \APM\APM.TXT


ΓòÉΓòÉΓòÉ 22. Test # 18  PCMCIA ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 22.1. Purpose ΓòÉΓòÉΓòÉ

Test OS/2 interface for PCMCIA slots and devices


ΓòÉΓòÉΓòÉ 22.2. Hardware/Software Requirements ΓòÉΓòÉΓòÉ

System has at least one (1) PCMCIA slot.


ΓòÉΓòÉΓòÉ 22.3. Installation ΓòÉΓòÉΓòÉ

The PCMCIA testcases were loaded at the beginning of this documentation. See
chapter on LOADING TEST CASES.

PCMCIA directory structure information

     PCMCIA - this readme, and output log files after execution

     TEXT  - text input files used by testcases

     UTIL  - utility programs

     CMD   - commands for testcases execution

     SCRIPT - testcase script files

     STRESS - testcase executables (.EXE FILES).


ΓòÉΓòÉΓòÉ 22.4. PCMCIA TEST INFORMATION ΓòÉΓòÉΓòÉ

PCMCIA testcases are set up to test the system interface to the PCMCIA slot.

Drive Assignments

The testcase sections assume that the C  D partitions are defined on fixed disk
and the test system has two (2) PCMCIA slots.

Note:

   1. Durning Phase 3 of OS/2 install (selective install), be sure to install
      all PCMCIA options (DISK, FLASH, MODEM)

   2. Refer to the Drives icon t determine drive letters assigned.


ΓòÉΓòÉΓòÉ 22.4.1. PCMCIA TESTCASE EXECUTION PROCESS ΓòÉΓòÉΓòÉ

The PCMCIA testcases exercise the 3 layers of OS/2 PCMCIA support.  The system
unit, socket services and card services layers are exercised with each of the
PCMCIA SVT testcases.

   1. Get to an OS/2 Full Screen session (PCM_TEST)

   2. Type D  and ENTER for testcase drive

   3. Type CD \PCMCIA and ENTER for PCMCIA directory

   4. Insert PCMCIA card to be tested in PCMCIA slot (ATA DISK, FLASH, SRAM)

 Based upon the type of the PCMCIA card inserted, enter one of the following
 commands to execute the testcases.

 ATA DRIVES Run Command Examples

           PCMCIA_A  E  or  PCMCIA_A  F  (Parameter is drive letter)
                Output Logs

                     \PCMCIA\ATA-DISK.LOG - should find 6 pass

                     \PCMICA\PCMCIA_A.LOG

                     \PCMCIA\FSCPYATA.LOG

                     \PCMCIA\FSDELATA.LOG

                     \PCMCIA\FSDIRATA.LOG

 FLASH DRIVES Run Command Examples

           PCMCIA_F  G  or  PCMCIA_F  I  (Parameter is drive letter)
                Output logs

                     \PCMCIA\SRAMCRD.LOG - should find 4 pass

 SRAM Run Command Examples

           PCMCIA_S  G  or  PCMCIA_S  I  (Parameter is drive letter)
                Output Logs

                     \PCMCIA\SRAMCRD.LOG - should find 4 pass

 PCMCIA FVT TEST RESULTS

 Test results will be collected automatically, see chapter on COLLECTING TEST
 RESULTS


ΓòÉΓòÉΓòÉ 23. Test # 19  SMP VERIFICATION TEST ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 23.1. Purpose ΓòÉΓòÉΓòÉ

To determine the number of processors in the SMP system and to verify the
processors are enabled.  This test is required for SMP systems only.

This test will require the operating system, OS/2 for Symmetrical
Multiprocessing (OS/2 for SMP) software to be installed prior to running this
test.  If you do not have this software, contact the OS/2 Compatibility Test
Program Office.

If OS/2 for SMP has not been installed, do not run this test.


ΓòÉΓòÉΓòÉ 23.2. Hardware/Software Requirements ΓòÉΓòÉΓòÉ

compac.

     An SMP system with at least one (1) processor installed and enabled

     OS/2 for SMP operating system installed.


ΓòÉΓòÉΓòÉ 23.3. Installation ΓòÉΓòÉΓòÉ

After the OS/2 for SMP operating system has been installed, you will need to
install the SMP testcase.  Run PCMSETUP from the CD-ROM or select EXTENSIONS
from diskette SETUP to install the SMP testcase.

After the files are copied to the D \SMP directory, please take the time to
read the 'README' file that has been copied to the test \SMP directory.


ΓòÉΓòÉΓòÉ 23.4. Test Process  - SMP ΓòÉΓòÉΓòÉ

compac.

   1. At the OS/2 FULL SCREEN prompt, in the D  Drive, type CD SMP and press
      ENTER

   2. At the OS/2 Full Screen prompt, in the D \SMP directory, type SMP001 and
      press ENTER

      Note:  Control will return to a Full Screen Command prompt.
 Results  Test results are written to the D \SMP directory in the form of a
 file; TEST.LOG.

 The following is an example of the output file, TEST.LOG on an SMP system that
 has two processors and they both are enabled. compac.

     SMP001 testing starting..........

     system has 2 processors

     *** Processor 1 Status is enabled. ***

     *** Processor 2 Status is enabled. ***

     testing status on processor 0.

     test passed, anticipated error occurred.

     testing status on a processor beyond actual number of processors.

     test passed, anticipated error occurred.

     testing status on processor 0.

     test passed, anticipated error occurred.

     testing status on a processor beyond actual number of processors.

     test passed, anticipated error occurred.

     testing status of null.

     test passed, anticipated error occurred.

     testing status greater than 1.

     test passed, anticipated error occurred.

     SMP testing ended..............
 Examine the output file, TEST.LOG for any messages that may indicate test
 failure by comparing the sample output as above to your output file.

 Error Files  As above

 Run Time Less than 1 minute.


ΓòÉΓòÉΓòÉ 24. Test # 20 SPEECH RECOGNITION-SPEECH ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 24.1. System Requirements ΓòÉΓòÉΓòÉ

     Pentium 90Mhz or higher
     16MB Memory
     300MB OS/2 Boot partition
     Sound Card (refer to WARP 4.0 readme for supported cards)
     Speakers
     Microphone (shipped with Version 4.0 PCM Testkit)


ΓòÉΓòÉΓòÉ 24.2. Install Verification ΓòÉΓòÉΓòÉ

   1. Click on "Programs" icon on desktop

   2. Verify that the "Voice Type" folder is present, Click to open.

   3. Verify that the following icons are in Voice Type folder

        a. Dictation Window

        b. Dictation Macro Editor

        c. Enrollment

        d. Voice Type Users Guide (shadow icon)

        e. States Game

        f. Migrate User Information

        g. Optional Vocabularies Install/Uninstall

        h. Check Installation

        i. Voice Manager

   4. Check Installation

        a. Click on "Check Installation" icon.

        b. Enter user name and click on "Create" button.

        c. Click on OK for pop-up that new user has been created successfully

        d. Click on "Start Test" button. Repeat the words presented in the
           display area. Continue until all 7 test words have been spoken and
           recognized. Test will stop when all 7 completed  Click "OK" on
           pop-up to establish that the test completed successfully.

        e. Click on "Check Speakers". Let recording play for at least 5 seconds
           then click "OK" to stop.

        f. Click on "Record. Pop-up will request at least 8 words, consistent
           volume, click "OK" Speak at least 8 words (a sentence) into
           microphone. Click on "Stop", then "Play" to playback the recording

        g. Click on "Exit" to close.

        h. Click on "YES" to save input and match level established.


ΓòÉΓòÉΓòÉ 24.3. Voice Test ΓòÉΓòÉΓòÉ

   1. Click on "States Game". Wait for application and Voice Manager to open
      and initialize.

   2. Click on Microphone in Voice Manager to activiate.

   3. Say the names of several states and verify that they are highlighed.

      Note:

        a. The "Help" button provides a list of state names and which have been
           spoken and recognized and which are left.

        b. It may be necessary to modify the voice settings for match. To to
           this, click on the Voice Manager icon to the left of the help icon
           (?).  Click on the Audio Tab and go to the second page.  Adjust the
           slide bar for sound match to the left for more approximate match.
           Then retry the States Game       .

   4. Close the States Game

   5. Verify that the microphone in Voice Manager is still active.


ΓòÉΓòÉΓòÉ 24.4. Desktop Navigation Test ΓòÉΓòÉΓòÉ

   1. Say "Jump to Command Prompts"

   2. Verify that the "Command Prompts" folder opens on desktop.

   3. Say UP/DOWN/LEFT/RIGHT as needed to highlight OS/2 window

   4. Say OPEN, verify that an OS/2 window session opens.

   5. Say CLOSE, when pop-up panel appears, say YES to continue closing.


ΓòÉΓòÉΓòÉ 25. Test # 20 SPEECH RECOGNITION TEST RESULTS WORKSHEET ΓòÉΓòÉΓòÉ

                      PCM Compatibility Testkit

                   WARP 4.0 - SPEECH RECOGNITION TEST




Inidate the status for each of the test scenarios with an "X"
in the appropriate column.



OS/2 speech installed correctly and folder objects found.   PASS__FAIL__
   Comments




Check Installation Test was successful, and new user was    PASS__FAIL__
created if not previously created through enrollment icon.
   Comments




States Game Test was successful.                            PASS__FAIL__
   Comments




Desktop Navigation Test was successful                      PASS__FAIL__
   Comments





Copied to Test Results Diskette - \APM\APM.TXT              PASS__FAIL__


ΓòÉΓòÉΓòÉ 26. PRINTING THIS DOCUMENT - README ΓòÉΓòÉΓòÉ

To print this document, go to the "Services Pulldown" and select "PRINT".
Before you hit print be sure your printer is turned on and you have enough
paper in the printer. The entire document is 80 pages and if you are printing
the entire document, it will take approximately 10 minutes to spool to the
printer. You will see the small clock icon on the display. Please be patient
and do not hit any keys or use the mouse during this period. Your system is not
hung.