Installation Requirements

Installation

No Install Program

There is no installation program for Kernel Trace. This omission is intentional, as the expected audience of this product is:

consultants and developers
large corporate IT departments

Since this audience is highly technical and the installations will most often be done on a large number of standardized machines, there is little value to a generic, graphical installation program.

Before starting the installation, it is critically important to have read the planning sections of this document. In particular, one must ensure that the prerequisites have been accommodated.

Installation Procedure

Insert the Kernel Trace for OS/2 CD in the CD-ROM drive or unzip the ktrace.zip file which you downloaded (depending upon your delivery media).

Execute one of the following copy commands:

COPY Z:\KTRACE\KTRACE.SYS X:\OS2\BOOT

COPY Z:\KTRACE\KTRACE.SYS X:\

where X: represents the boot drive and Z: represents the drive letter assigned to the CD-ROM drive or the partition onto which ktrace.zip was unzipped (depending upon your delivery media).

Create a directory for KTRACE, for example, C:\KTRACE.

Copy the files KTRACE.CFG, KTRACE.EXE, and LICENSE.KTO into the directory created in the previous step.

Note:

Optional

Edit the KTRACE.CFG file to contain user-defined default values (see the Configuration section for more details).
KTRACE.CFG and LICENSE.KTO can be located separately from KTRACE.EXE; see the File Listing for the locations and order KTRACE will use when searching for these files.

Locate the CONFIG.SYS in the root directory of the boot drive. Add the following statement to your CONFIG.SYS:

BASEDEV=KTRACE.SYS

This line is the sole, required change to the system's configuration to enable KTRACE. This device driver MUST be loaded as a BASEDEV, which means it is loaded at a very early point in the system's IPL. This also means that the driver must reside in either the root directory of the boot drive (e.g., C:\) or in the \OS2\BOOT directory on the boot drive. OS/2 cannot find BASEDEV drivers if they do not reside in one of these two directories.

Optional

SET PATH

CONFIG.SYS

SET PATH=<Current Path>;Y:\KTRACE;

where <Current Path> is the complete path currently set in CONFIG.SYS and Y: is the drive where the KTRACE directory resides.

Reboot the system.

If the device driver is successfully loaded, the following output will be visible during the machine's boot sequence:

Locked Files

None of the Kernel Trace modules are locked, including the device driver. This means that the distribution of changes is as easy as replacing these files with newer versions.