## Using Your DDK

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

### 32-Bit Font Test Tool

Tool Description:

32-Bit Font Test is used to browse and output text files on local or remote output devices using any public font. From the source code provided an OS/2 for Intel tool can be created.

Font Test also allows the user to view various capabilities of the device attached to the selected queue, including font and hardcopy information. Files are printed to the selected queue with any print options saved in Font Test, such as font, color, and text format. Font Test can be invoked to print a file from an OS/2 command line using the queue and print options that were saved from the Font Test's PM Interface. Font Test provides extensive help facilities for operation from a PM session.

Compilers/Assemblers Required:

         IBM CSet ++ V2.01 Compiler

Build Instructions:

Note:

When building, we have found that VDISKs as large as 2MB have caused build breaks. If your TMP variable is set to a VDISK, it is advisable to reset it to a hard drive before building.

1.Set the environment variables so that the correct tools are picked up during the build.

    e.g., SET PATH=<drive>:\DDK\TOOLS;%PATH%

Where <drive> represents your DDK installed drive and DDK represents the DDK installed directory. On the CD-ROM, the TOOLS directory path is DDK\ TOOLS.

2.Before the FIRST build is attempted, run (only once) the COPYCSET.CMD REXX command file in the DDK\TOOLS directory. This command copies the set of needed files from your copy of the IBM C Set ++ V2.01 compiler to the proper directories under the DDK base directory.

    e.g., COPYCSET <IBMCdrive>:\'IBMC' <drive>:\DDK

Where <IBMCdrive> represents the IBM C Set ++ V2.01 installed drive and ' IBMC' represents the IBM C Set ++ V2.01 installed directory, <drive> represents your DDK installed drive and DDK represents the DDK installed directory.

3.Change the directory to DDK\PRINT\SRC\OSDD\FT32

4.Use the following NMAKE example to create the appropriate device driver:

      e.g., "NMAKE RETOS2C ddkbld=1 > FT32.ERR 2>&1"
      where:
            "NMAKE is the build tool
            "RETOS2C" creates a retail driver
            "> FT32.ERR 2>&1" redirects all output to a file

       NMAKE RETOS2C ddkbld=1 > FT32.ERR 2>&1  (This builds the retail driver)
       NMAKE DBGOS2C ddkbld=1 > FT32.ERR 2>&1  (This builds the debug driver)

Files Created by Successful Build:

         Retail Version:
         Directory:  \DDK\PRINT\SRC\OSDD\FT32\RETAIL

         o  FT32.EXE
         o  FT32.HLP

         Debug Version:
         Directory:  \DDK\PRINT\SRC\OSDD\FT32\DEBUG

         o  FT32.EXE
         o  FT32.HLP