## MMPM/2 Device Driver Reference

[prev][next][parent][TOC]

### Setting Up the Environment for Running Test Suites

Before using the audio or video test suites with the P2STRING tool, do the following:

1.Make sure that OS/2 2.1 and the adapter to be tested are installed.

2.Update the CONFIG.SYS file.

All the test suites use environment variable to determine the location of the input data files. Add the following SET statements to the CONFIG.SYS file.

    SET MMDATA=<path>

    SET MMDATA-AUD=<path>

    SET TESTDATA=<path>

The path for MMDATA and MMDATA-AUD must specify the path to the audio input files. For example, your .WAV or .MID files. The path for TESTDATA must specify a path to a temporary working directory that you create.

The following files must be loaded, and their path must be specified in the CONFIG.SYS file:

SETENV.CMD
RESETINI.CMD
HWCODE.CMD
P2STRING.EXE
P2S_DLL.DLL

3.Shut down and restart your workstation so the CONFIG.SYS parameters will take effect.

4.Run HWCODE.CMD for each test suite to be tested.

This file is in the IBM Developer Connection Device Driver Kit for OS/2 HWCODE.CMD is a REXX command that determines each test case's exact hardware needs and displays the results. The test case's name contains information that HWCODE.CMD uses to make these determinations, so it is important not to change the name of the test case.

The syntax for HWCODE.CMD is:

    HWCODE <Test Case Name>

Note: The Test Case Name must include the file name extension. HWCODE.CMD displays the brand and model of audio and video adapters currently supported by OS/2 2.1. The adapter being tested is not listed if it is new , but this information is useful for comparing results based on expected compatibility with other manufactures.

HWCODE.CMD also displays audio and video hardware codes.