# Chapter 8. PCM Base Test Case Details

Use the instructions in this chapter to run those tests that must be run individually or to rerun individual tests.

The following information is included, where appropriate, for each test:

- The name of the test, or part of the test

- A description of the test

- The steps to run the test

- The test results

- The test duration

## Base Test Summary

The following table lists the tests in the base testkit, where to get the details about each test case, and the approximate run time.

Table 2. Summary of Base Tests

Test | Description | Approximate Run Time
SNF001 | OS/2 System Installation and Initialization on page 40 | 60 Minutes
SNF002 | File I/O Using Semaphores Test on page 41 | 10 Minutes
SNF006 | Code Page Switching (VIDEO/PRINTER) Test on page 41 | 5 Minutes
SNF007 | Shared Segments Test on page 42 | 5 Minutes
SNFBPB | High Performance File System Test on page 42 | 5 Minutes
SNFREXX | Batch Processing and REXX Calls on page 42 | 3 Minutes
SNFMVDM | Automated Tests to Stress the Base System on page 44 | 15 Minutes
SNFWIN | Your DOS/Windows Applications Test on page 44 | 30 Minutes
PCMMED01 | Stress Test on page 45 | 6 Hours
KBD | Keyboard Device Driver Test on page 46 | 5 Minutes
FVTDISK | Disk Multitasking Test on page 47 | 20 Minutes
FORMAT | Format Utility Test on page 48 | 15 Minutes
TIMERDD | Timer Device Driver Test on page 48 | 10 Minutes
PRINTDD | Printer Device Driver Test on page 49 | 20 Minutes
PCM_VGA PCM_SVGA PCM_HPFS PCM_CD PCM_FLC PCM_REXX | OS/2 Multimedia Test on page 50 | 10-20 Minutes Each
SNFAPM | APM Test on page 53 | 60 Minutes
SNFPCM | PCMCIA TEST on page 55 | 30 Minutes
SNFSMP | OS/2 for SMP Test on page 56 | 2 Minutes
SPEECH | Voice Navigation on page 57 | 30 Minutes
JFSTEST | Test JFS File System on page 52 | 30 Minutes

## System Hardware Configuration (SNF001)

You must include a definition of your hardware in the material submitted to the Program Office on the results diskette. The RESULTS process checks for this information. An error will be posted for Test # 1.

### Creating the Hardware Information

Double-click on the PCM KIT icon, and then double-click on the PCM HDW icon.

The System Hardware Information window is displayed. Click on Update System Information and complete each of the hardware information component. (See Appendix D, "Hardware Information Components" for a representation of each panel.)

When complete, click on Save and Exit. After you complete a page and continue to the next page or have saved and exited, you can modify the entries by restarting PCM HDW. You can then update the displayed information.

### Results

The machine.txt file is created and saved in the \snf001 subdirectory for all the system configuration data.

You can enter this information before or after running any tests. However, it must be created before you collect your results as described in Chapter 7, "Collecting and Submitting Test Results".

## File I/O Using Semaphores (SNF002)

This is a test of semaphores, video I/O, file I/O, and interprocess communications. It also tests for semaphores output from the kernel test.

### SNF002 Test Steps

1. At an OS/2 command line, change to the d: drive.

2. Type cd batch and press Enter.

3. Type SNF002 and press Enter.

4. The test displays:

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

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

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

There should be 59 entries

D:\ACCEPT\CORE\SNF002.LOG: 59

1. You are returned to the test drive prompt.

### Results of SNF002

Check the d:\accept\core\snf002.log file. If there are not 59 entries, check the log to see which files did not pass.

If any file shows "FAIL", shut down and reboot the system; then, rerun the entire test.

### Run Time

The test takes approximately five minutes.

## Code Page Switching (Video/Printer) (SNF006)

This is a comprehensive test of objects within folders, and the display of ASCII codes with a range of different background colors.

Check the Desktop for the printer icon. A printer needs to be installed for this test even if no printer is attached to the system.

### SNF006 Test Steps

1. Open an OS/2 Full Screen session and change to the d: drive.

2. Type cd batch and press Enter.

3. Type snf006 and press Enter.

4. The test displays all the ASCII characters and begins to change colors.

5. The test returns to the d:\batch directory at completion.

### Results of SNF006

The test results are stored in the following files in the d:\nlscpa directory:

- fontd

- printd

- cpalog

- switch_6

Each file ends with `PASS`, `SUCCESSFUL`, or `FAIL`.

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

### Run Time

Approximately five minutes.

## Shared Segments Test (SNF007)

This is a test of multiple memory allocation calls

### SNF007 Test Steps

1. At an OS/2 command line, change to the d: drive.

2. Type cd batch and press Enter.

3. Type snf007 and press Enter.

4. The test runs and returns to the test drive prompt.

### Results of SNF007

Check the d:\loga\switch_7 file for `PASS` or `FAIL` information for:

- M32SHR

- NAMESHR

- GIVESHR

- GETSHR

### Run Time

Approximately 10 minutes.

## High Performance File System Test (SNFBPB)

This is a test of the HPFS file system.

### SNFBPB Test Steps

1. At an OS/2 command prompt, type chkdsk c: /f: 3. Verify that there are no disk errors for each HPFS partition before starting the test. The test might fail otherwise.

2. Change to the d: drive.

3. Type cd batch and press Enter.

4. Type SNFBPB and press Enter.

Note: | The snfbpb.cmd command looks at c:, d:, e: and f: for the first HPFS partition it finds. If all these partitions are FAT, the test ends and OS/2 returns to the d:\batch subdirectory.

1. If an HPFS partition is found, the test verifies that the directory displays long file names, because HPFS allows file names up to 256 characters.

2. The test ends and returns to an OS/2 command line.

### Results of SNFBPB

The batch\snfbpb_l log file indicates `PASS`, `FAIL`, or `NO HPFS`.

### Run Time

Approximately five minutes.

## Batch Processing and REXX Calls (SNFREXX)

This test verifies the REXX language with OS/2.

### SNFREXX Test Steps

1. At the OS/2 command line, change to the d: drive.

2. Type cd batch and press Enter.

3. Type snfrexx and press Enter.

4. Two system errors (sys 1041) are displayed during the test. They are designed to fail, and do not indicate test failure.

5. You are returned to the OS/2 command line.

### Results of SNFREXX

1. At test end, a message is displayed: `scanning output log REXX_LOG for "OK"`

2. `d:\rexx\rexx_log: 71` is displayed.

The rexx_log file is in the \rexx directory. If there are not 71 entries, type type rexx_log |more and inspect each command line for `BAD`.

### Run Time

Approximately three minutes.

## Automated VDM Test (SNFMVDM)

This is a collection of small tests. You must have a mouse attached to the system.

### SNFMVDM Test Process

1. At an OS/2 command line, change to the d: drive.

2. Type cd batch and press Enter.

3. Type snfmvdm and press Enter.

4. Do not touch the keyboard or mouse until Logical Screen Group 1 is visible on the Desktop with flashing colors and characters.

Note: | The box with the flashing colors appears once on the Desktop, goes away momentarily, and then appears again. This might happen rather quickly, depending upon the speed of the machine.

1. After the second window of flashing colors appears for a full five minutes, press Q to end the video part of the test.

2. The test ends, the window closes, and you are returned to the OS/2 command line.

### Results of SNFMVDM

At the end of the test, the message is displayed:

    Checking output logs under \vdm for "PASS"

    There should be 6 files with PASS

The results files in the \vdm directory are:

- SWITCH_V

- VDM1 (partial is OK)

- VVTATXM4

- FLT018

- MAT015

- CTTCLOCK

### Run Time

Approximately 15 minutes.

## Your DOS/Windows Applications Test (SNFWIN)

This is a test of your Windows 3.1 and 3.11 compatible applications.

To be able to run this test, you must first load your Windows applications in the d:\window directory.

Windows applications are not provided with this test package. You must provide your own DOS/Windows applications.

### SNFWIN Test Steps

There are two ways to get a Windows environment. Do one of the following:

- Select WIN-OS/2 Full Screen in the Command Prompts folder, which is located in the OS/2 System folder.

- Type winos2 from an OS/2 full screen session.

Either method results in a Windows Program Manager screen.

Do the following steps:

1. Select File from the Program Manager action bar.

2. Select Run from the pull-down menu. (Select Exit Win-OS/2 to return to an OS/2 session.)

3. Type the name of the Windows program you want to run and press Enter.

4. (If you press Ctrl+Esc, the Task List window is displayed where you can select Desktop to return to an OS/2 session.)

### Results of SNFWIN

Your Windows application should run without errors.

Because this test is visually verified by the tester, no specific output files are generated.

After completing this test you will need to modify the log file, c:\pcmlog\snfwin.txt with the results.

You also need to add the applications and the version that was used in the testing to this log.

### Run Time

The run time depends upon your applications.

## Stress Test (PCMMED01)

This set of tests collectively tests 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.

This test runs for approximately six hours. After you start this test, the test systems should be left alone until the test completes. These tests might fail if there is 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.

### PCMMED01 Stress Test Steps

1. Shut down and reboot the system.

2. After restarting, the PCM TEST screen is displayed.

3. Press 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.

4. At an OS/2 command prompt, type d:\log and press Enter.

5. Type run and press Enter. (The PCMMED01 test script is run.)

6. After a few moments, the screen clears and then displays three bars.

7. Insert a blank diskette and press any key to continue.

Note: | Press Ctrl+C to terminate the test here if you do not want to continue.

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

2. At test completion you are returned to an OS/2 full screen session or to the Desktop.

### Results of PCMMED01

Errors encountered that prevent test completion as well as errors reported in the summary file could indicate test failure.

At completion time, go to an OS/2 command prompt and change to the d:\log directory. Type type pcmmed01.sum and press Enter.

After 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

In some cases the dswitchm or cube files will report a <PARTIAL>. This is acceptable; your passing count will be one or two less. The <PARTIAL> is caused if the switcher script stops the test before completion.

Note: | If partials are detected other than in dswitchm or cube, rerun the individual testcase.exe with the same parameters as used in PCMMED01. Then run strlog.cmd to update the summary file.

### Rerunning the Stress Test

If you do not achieve the desired test results described above, do one of the following:

- Make certain the test system does not have other activity while running the stress test.

- Rerun the stress test.

- Reload the stress tests and rerun the stress test.

- Refer to the STRESS HELP file on the Web Tips page for help solving individual file failures, or refer to the data in the document on the bulletin board information.

### Run Time

The stress test takes approximately six hours.

## Keyboard Device Driver Tests (KBD)

These tests exercise the USB keyboard and non-USB keyboard device driver.

### KBD Test Steps

1. Open an OS/2 window session.

Note: | The testcase should not be run in full screen mode.

1. Enlarge the OS/2 window so that you can see the questions on the screen as they are presented.

2. Do not enter any keystrokes until prompted.

3. At an OS/2 command prompt, change to the \kbd directory on the d: drive.

4. At the command prompt, type:

vio.cmd

1. Follow the instructions on the display to select the keyboard type and enter the keystrokes when prompted.

2. When the test is complete, you are returned to d:\kbd directory.

### Results of KBD

The test writes its results in the following log files:

- d:\kbd\kbd.log for standard keyboard

- d:\kbd\kbd1.log and d:\kbd\kbd2.log for USB keyboard

To determine if the tests were successful, search the file for the status indicators.

To verify that the vio.cmd test for standard keyboard was successful, type:

    grep "STATUS KBD" kbd.log

The output should be similar to the following:

    STATUS .... RUN 35....PASS 35...FAIL 0...AUTOFAIL 0

To verify that the vio.cmd test for USB keyboard was successful, type:

    grep "STATUS KBD" kbd1.log

    grep "STATUS KBD" kbd2.log

The output should be similar to the following:

    STATUS .... RUN 35....PASS 35...FAIL 0...AUTOFAIL 0

### Run Time

The total run time for the KBD test is approximately 5 minutes.

## Disk Multitasking Test (FVTDISK)

This test exercises the file system's use of drive d:.

### FVTDISK Steps

From an OS/2 command prompt, change to the \cmd directory, type fvtdisk and press Enter.

Note: | All the parameters for FVTDISK are in fvtdisk.cmd 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 of FVTDISK

FVTDISK creates log files named d:\logf\dasdstd1.log and d:\logf\dasdstd2.log.

### Run Time

Approximately 15 minutes.

## FORMAT Utility Test (FORMAT)

This test verifies the FORMAT function for various diskette types.

The FORMAT utility tests run both the OS/2 .cmd test cases and the DOS .bat test cases.

Note: | This test program can test both 5.25-inch and 3.5-inch diskettes.

### FORMAT Test Steps

1. Shut down and reboot the system.

2. The tests assume that the 1.44 MB or the 1.2 MB drive is the a: drive. If your configuration is different, edit the .inp file and change the drive letter on both the command line and FTEST line of the input files.

3. Open an OS/2 full screen session (change to the PCM TEST window if active).

4. Place a blank diskette in the a: drive.

5. If drive a: is 1.44 MB diskette drive then:

- Type cd format and press Enter.

- Type tst1_44.cmd and press Enter.

1. If drive a: is 1.2 MB diskette drive then:

- Type cd format and press Enter.

- Type tst1_2.cmd and press Enter.

### Results of Format

The output .log files are scanned using grep.exe to look for the STATUS lines to provide summary PASS/FAIL status. 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.

- Type type flop144.log or type flop525.log.

- Type type dsktrslt.log.

### Run Time

Approximately 20 minutes for each drive media.

## Timer Device Driver Test (TIMERDD)

The timer device driver consists of one testcase:

- DH 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.

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

### TIMERDD Test Steps

1. At an OS/2 command line, type cd timerdd and press Enter.

2. Type timer and press Enter.

3. Control is returned to the d:\timerdd directory.

### Results of TIMERDD

DH test results are stored in the timerdd\dh\dh directory.

Type type dh.log |more and press Enter.

Look at each file for each of the 18 variations to determine success or failure. They will not run consecutively.

### Run Time

Approximately five minutes for the dh.exe test.

## Printer Device Driver Test (PRINTDD)

This is a test for printer device drivers to the parallel ports LPT1, LPT2, or LPT3. You can test these ports individually or collectively.

### PRINTDD Test Steps

Connect a printer to the LPT ports you want to test.

#### OS/2 Full Screen Printer Testing

1. Open an OS/2 full screen session.

2. Change to the \printdd directory on the d: drive

- To test LPT1 only, type print1.cmd and press Enter. This test is required.

- To test LPT2 only, type print2.cmd and press Enter. This test is optional.

- To test LPT3 only, type print3.cmd and press Enter. This test is optional.

- To test LPT1 and LPT2, type print1_2.cmd and press Enter. This test is optional.

- To test LPT1 and LPT3, type print1_3.cmd and press Enter. This test is optional.

- To test LPT2 and LPT3, type print2_3.cmd and press Enter. This test is optional.

- To test LPT1, LPT2, and LPT3, type printall.cmd and press Enter. This test is optional.

1. At test end, control is returned to the OS/2 full screen session.

#### 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.bat and press Enter. This test is required.

- To test LPT2 only, type print2.bat and press Enter. This test is optional.

- To test LPT3 only, type print3.bat and press Enter. This test is optional.

- To test LPT1 and LPT2, type print1_2.bat and press Enter. This test is optional.

- To test LPT1 and LPT3, type print1_3.bat and press Enter. This test is optional.

- To test LPT2 and LPT3, type print2_3.bat and press Enter. This test is optional.

- To test LPT1, LPT2 and LPT3, type printall.bat and press Enter. This test is optional.

1. At test end, press Ctrl+Esc to open the Task List window and click on waiting DOS PRINT test.

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

### Results of PRINTDD

To view test output, type the file you want to check. For example, type type prt1os.log to display `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

- 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.

## OS/2 Multimedia Tests

These tests verify the functions of the various Multimedia Presentation Manager/2 (MMPM/2) components. They are a minimal representative test for multimedia usability in which they exercise the wave audio, MIDI, CD and digital video devices.

### Multimedia Requirements

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

### Automated Test Steps

The Multimedia tests run unattended if selected from the Selection & Execution GUI screen.

If the test system has sound support:

- If Testkit drive is HPFS, you must run PCM_HPFS.

- If your video is VGA (resolution less than 1024 × 768 × 256), you must run PCM_VGA.

- If your video is SVGA (resolution at least 1024 × 768 × 256), you must run PCM_SVGA.

- You must run PCM_FLC.

- You must run PCM_REXX.

These test selections require a music CD in the CD-ROM drive.

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

- When all tests have been selected, click on RUN.

Note: | If the test system has sound support and a CD-ROM that supports streaming, then you can also run PCM_CDS. This test is optional, and should not be run until required testing has completed, and the results diskette is ready for submission.

### Individual Test Steps

Before running these tests, type buc and press Enter to change to the cd\build\src\svt\buckcmd directory.

If the test system has sound support:

- For PCM_HPFS, type pcm_hpfs.cmd and press Enter.

- For PCM_VGA, type runmme pcm_vga and press Enter.

- For PCM_SVGA, type runmme pcm_svga and press Enter.

- For PCM_FLC, type runmme pcm_flc and press Enter.

- For PCM_REXX, type pcm_rexx.cmd and press Enter.

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

- For PCM_CD, type runmme pcm_cd and press Enter.

- For PCM_CDS, type runmme pcm_cdst and press Enter.

- As each test ends, the script file returns to an OS/2 full screen session.

### Test Results

The test results are in the d:\results\mmepcm\svtraw directory. Log files are in the d:\results\mmepcm\svtlog directory and have the same name as the output files but end with the .log extension.

- The pcm_svga.ra_ file contains the SVGA results.

- The pcm_vga.ra_ file contains the VGA results.

- The pcm_hpfs.ra_ file contains the HPFS results.

- The pcm_cd.ra_ file contains the CD Music results.

- The pcm_cds.ra_ file contains the CDS Music results.

- The pcm_flc.ra_ file contains the FLC results.

- The rexxrsp.out file contains the PMREXX results.

Note: | There will be a total of: 11 TESTS for PCM_VGA 12 TESTS for PCM_SVGA 1 TEST for PCM_HPFS 2 TESTS FOR PCM_FLC 7 TESTS for PCM_CD 6 TESTS for PCM_CDS 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 resetlog command from the d:\util directory. This .cmd file deletes all files generated by these tests.

### Run Time

Test duration is approximately 30 minutes for each test.

## OS/2 Journaled File System Test (PCMJFS)

This test is run on the Additional Server (S01).

This is a test of the OS/2 Journaled File System (JFS) that is run only when testing OS/2 Warp Server for e-business which implements JFS support. Do not run this testcase with other OS/2 products. This is a testcase that uses a REXX command file to format the JFS partition, and run a series of file system commands on the JFS file partitiion. The default drive letter is E: as specified by system installation instructions which would have the assigned the E: drive letter to the JFS Volume/Partition under LVM.

This testcase will also cover LVM functions of having volumes span disk partitions on the same disk drive, or on 2 different disk drives.

If you run the PCMJFS testcase from the PCM_TEST PM GUI, you can specify a different drive letter as the JFS Volume/Partition to be tested.

Note: | This will format the drive letter provided, be sure it is the drive letter for the JFS Volume/Partition that was setup during OS/2 installation.

### PCMJFS Test Steps

1. At an OS/2 command line, change to the d: drive.

2. Type cd batch and press Enter.

3. Type pcmjfs e and press Enter.

4. The test runs and returns to the test drive prompt when through.

5. The command Line parameters for PCMJFS.CMD have been hard coded to call the test routine \JFSTEST\FLSPGM1.CMD as follows:

- /H:MB (File size to be created: KB or MB or GB or #bytes)

- /per:90 (Percentage of freespace to be filled: 0->100 Default 90%)

- /num:1 (number of drives: Default is 1)

- /dl:E (JFS Drive letter, Default is E)

- /FSDir:JDIR (Dir name to create: Default is DIR)

- /FName:JFILE (File name to create: Default is FILE)

- /iter:1 (no of iterations: Default is 1)

### Results of PCMJFS

This test is successful if the system successfully formats and exercises the JFS Volume (spanning 2 partitions, which can be on different disks).

Check the d:\jfstest\jfstest.log for `PASS` or `FAIL` information for the testcase.

### Run Time

Approximately 30 minutes.

## Advanced Power Management Test (APM)

The APM test is intended for portable systems that utilize batteries for power.

This test tests both APM hardware and aspects of the PM user interface including:

- Power state definitions

- 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 refresh functions work correctly

Note: | Non-APM Supporting Hardware: If Selective Install is used 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.

### APM Test Steps

The following set of APM test steps describes a brief test of the APM functions installed 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 three to five minutes and suspend timer to 15 minutes or more.

3. Verify the following are present in config.sys.

OS/2 Warp Version 4.0

- DEVICE=C:\OS2\BOOT\APM.SYS

- DEVICE=C:\OS2\MDOS\VAPM.SYS

1. Verify that Power Object is in System Setup folder.

2. Open an OS/2 window and insert a scratch diskette in the a: drive. From the d:\cmd directory, type drain.cmd.

3. Open the OS/2 System Setup folder and double-click on the Power Object.

4. Verify that the system shows "AC Powered" and "Battery State High."

5. Unplug A/C Charger.

6. Click on system menu for Power Object and select Refresh Now.

7. Verify that system shows "Battery Powered" and "Battery State High."

8. Allow the system time to enter standby mode (screen blanks).

9. Press any key to bring system out of standby mode, and verify that drain.cmd is still running (let it run for a couple of minutes).

10. Click on system menu for Power Object and select Suspend. Select Yes on the pop-up menu to continue suspend operation.

11. Press any key to bring system out of suspend mode, verify that the Desktop is OK, and that drain.cmd continues running.

12. Click on system menu for Power Object and select Refresh to bring up the submenu, and select On to set up automatic refresh.

13. Open the Power Object Settings/Properties. Click on the View tab, set refresh on, and refresh rate to 1-2 minutes.

14. Let the system run for 30 minutes, verify that the battery life bar shows an indication of battery drain.

15. Plug in A/C charger, wait for automatic refresh to occur (1-2 minutes) and verify that Power Object now shows "AC powered."

16. Stop drain.cmd in OS/2 window by pressing Ctrl+Break.

17. Let battery charge for 30 minutes or more.

18. Verify that Power Object battery life indicates increased charge.

19. Close Power Object.

20. Update the file \APM\APM.TXT on the testcase partition.

### Results of APM

Because this test is verified by the tester, no specific output files were generated. To obtain OS/2 Compatibility for Advanced Power Management, complete the information in the apm.txt file. You can print the apm.txt file to check off during the test and to update the file after completion.

## Advanced Power Management Test (APM) for Desktop Systems

This test tests both APM hardware and aspects of the PM user interface including:

- APM installed correctly and power object found

- Power object shows correct status for A/C power

- Standby and Suspend/Resume modes work correctly

- Power off mode work correctly

Note: | Non-APM Supporting Hardware: If Selective Install is used 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.

### APM Test Steps for Desktop Systems

The following set of APM test steps describes a brief test of the APM functions installed on a Desktop system with the OS/2 operating system.

1. Set hardware timers for screen blanking to 3-5 minutes and suspend timer to 15min or more.

2. Verify the following are present in config.sys.

OS/2 Warp Version 4.0

- DEVICE=C:\OS2\BOOT\APM.SYS

- DEVICE=C:\OS2\MDOS\VAPM.SYS

1. Verify that Power Object is in System Setup folder.

2. Open the OS/2 System Setup folder and double click on the Power Object.

3. Verify that the system shows "AC Powered".

4. Allow the system time to enter standby mode (screen blanks).

5. Touch key(s) to bring system out of standby mode.

6. Click on system menu for Power Object and select "Suspend", answer "Yes" on pop-up menu to continue suspend operation.

7. Touch key(s) to bring system out of suspend mode.

8. Click on system menu for Power Object and select "Power off", answer "Yes" on pop-up menu to continue shutdown operation.

9. Write result to apmdesk.txt file.

### Results of APM for Desktop Systems

Because this test is verified by the tester, no specific output files were generated. To obtain OS/2 Compatibility for Advanced Power Management, complete the information in the apmdesk.txt file. You can print the apmdesk.txt file to check off during the test and to update the file after completion.

## PCMCIA

This is a test of the OS/2 interface for PCMCIA slots and devices.

The test case sections assume that the C and D partitions are defined on the hard disk and the test system has two PCMCIA slots.

Note: | During Phase 3 of OS/2 installation (selective install), be sure to install all PCMCIA options (DISK, FLASH, MODEM). Double-click on the Drives icon to determine the drive letters assigned.

### PCMCIA Test Steps

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

1. At an OS/2 command line, change to the d: drive.

2. Type cd pcmcia and press Enter.

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

Type the appropriate command for the PCMCIA card to be tested: (Parameters are drive letters)

- ATA Drives

Run Command Examples: pcmcia_a e or pcmcia_a f

- FLASH Drives

Run Command Examples: pcmcia_f g or pcmcia_f i

- SRAM

Run Command Examples: pcmcia_s g or pcmcia_s i

### Results of PCMCIA

Output Logs:

\pcmcia\ata-disk.log - should find 6 pass

\pcmcia\pcmcia_a.log

\pcmcia\fscpyata.log

\pcmcia\fsdelata.log

\pcmcia\fsdirata.log

\pcmcia\flashcrd.log - should find 4 pass

\pcmcia\sramcrd.log - should find 4 pass

## SMP Verification Test

This test determines the number of processors in the SMP system and verifies that the processors are enabled. This test is required only for SMP systems.

You must install OS/2 Warp Server for e-business with SMP support or the Convenience Package for OS/2 Warp Server for e-business with SMP support on your system prior to running the test.

If OS/2 Warp Server for e-business with SMP support on the Convenience Package for OS/2 Warp Server for e-business with SMP support has not been installed, do not run this test.

### Hardware and Software Requirements

- An SMP system with at least two processors installed and enabled

- OS/2 Warp Server for e-business with SMP support or the Convenience Package for OS/2 Warp Server for e-business with SMP support installed

### Installation

After the operating system has been installed, install the SMP test case. Run PCMSETUP to install the testcase if not previously installed and select the SMP test cases.

### SMP Test Steps

1. At an OS/2 full screen prompt, change to the d: drive, type cd smp, and press Enter.

2. Type smptst and press Enter.

3. Control returns to an OS/2 command prompt.

### Results of SMP

Test results are written to the d:\smp directory in the smptest.log file.

The following is an example of the smptest.log output file on an SMP system that has two processors that are both enabled.

    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 smptest.log file for any messages that may indicate test failure by comparing the sample output to your output file.

### Run Time

Less than one minute.

## Speech Recognition (SPEECH)

### System Requirements

- Intel Pentium 90 MHz or faster

- 16 MB memory

- 300 MB OS/2 boot partition

- Sound card (refer to the OS/2 Warp 4.0 readme for a list of supported cards)

- Speakers

- Microphone

#### Installation Verification

1. Double-click on the Programs icon on Desktop.

2. Verify that the VoiceType folder is present. Open the folder.

3. Verify that the following icons are in VoiceType folder:

- Dictation Window

- Dictation Macro Editor

- Enrollment

- VoiceType Users Guide (shadow icon)

- States Game

- Migrate User Information

- Optional Vocabularies Install/Uninstall

- Check Installation

- Voice Manager

4. Check Installation:

- Double-click on Check Installation icon.

- Enter user name and click on Create.

- Click on OK in pop-up window indicating that new user has been created successfully.

- Click on Start Test. Repeat the words presented in the display area. Continue until all seven test words have been spoken and recognized. The test will stop when all seven are completed. Click on OK in pop-up window indicating that the test completed successfully.

- Click on Check Speakers. Let recording play for at least five seconds and then click on OK to stop.

- Click on Record. The pop-up will request that you read at least eight words, using consistent volume. Then, click on OK. Speak at least eight words (a sentence) into microphone. Click on Stop, and then click on Play to play back the recording.

- Click on Exit to close.

- Click on YES to save input and match level established.

#### 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 activate.

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

Note: | The Help button provides a list of state names and indicates which have been spoken and recognized. It might be necessary to modify the voice settings for match. To do 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.

1. Close the States Game.

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

#### Desktop Navigation Test:

1. Say "Jump to Command Prompts."

2. Verify that the Command Prompts folder opens on the Desktop.

3. Say Up/Down/Left/Right as needed to highlight OS/2 window.

4. Say "Open," and verify that an OS/2 window opens.

5. Say "Close" and when pop-up panel is displayed, say "Yes" to continue closing.

### Results of SPEECH Tests

Update the file \SPEECH\SPEECH.TXT on the testcase partition.

Because this test is verified by the tester, no specific output files were generated. To obtain OS/2 Compatibility for Speech Recognition, complete the information in the speech.txt file. You can print the speech.txt file to check off during the test and to update the file after completion.