KENTCURS

This utility sets up flags and version information that is stored in the header of a program file. The version information can be displayed by the PROGDATE utility, or, on most versions of Windows, using the Version tab in the Properties Dialog for the file. An example of the output from PROGDATE is shown below.

DP4 File Version Details and Verification Utility

File           CKS   Version           Date        Class      Release Status
                                       Comment
c:\dp4\WIN\SRVW32.EXE
               31322 4.620(006)500 102 11 Apr 2003 Standard   Release    WIN32

KENTCURS can be used on files containing a DP4 version stamp. Programs written in C/C++ which are linked with the DP4 C "CCOWN" library will always contain this, and you can add one to other C/C++ programs by including the verstamp.c file in the set of source files for the program.

If a Windows application or DLL contains a Windows version resource, KENTCURS will also set the information in the resource using data from the DP4 version information.

The command tails for KENTCURS are shown below:

Command Tail

Description

filenames

Specify the files to be maintained

−READ filename

Take the filenames from the named file

−CLASS suffix

Set the program class as follows (specify the initial or the full suffix):

suffix	class
STD	Standard
ADDITIONAL	Additional
KOREA	Korean
JAPAN	Japanese

This is used to distinguish various special builds of DP4 from the "standard" release

−DATE

Set the issue date to the current date

−FILEDATE

Set the PROGDATE date to the file date

−VERSION n

Set version number to n (This the number displayed after 4. in PROGDATE, 620 in the example above)

−LEVEL n

Set patch level number to n (This is the number displayed in parentheses after the version by PROGDATE, (006) in the example above)

−BUILD n

Set build number to n. This is displayed after the patch level by PROGDATE, (500 in the example above). In standard DP4 utilities it is only used to indicate the "build family" of the program. The Build Number as displayed in the version resource is set using the -internal option

−INTERNAL n

Set "internal number" to n. PROGDATE displays this number immediately before the program date, (102 in the example above). For standard DP4 utilities it is the most important version number as it allows us to identify the exact set of files used to build the program.

−STATUS n

Set the status to number n or ALPHA or BETA or RELEASE

−NOPAUSE

To prevent pause at the end

The following options apply to 16 bit executables only:

−NOCONVERT	Disable operating system conversion
−MAXSTACK
−STACK SIZE	Set stack size (hex)

The following options apply to OS2 executables only:

−OS2	Set corresponding property in OS/2 header;
−COMPAT

The following options apply to WIN32 executables only:

−WINDOWS	Program will detach from console window if started from console
−CONSOLE	Program remains attached to console if started from console windows or create a console if started from a program that does not have a console. You may need to set DP4 executables to be CONSOLE programs if you want to run via Telnet.

The following options apply to UNIX/Linux programs only:

−PATCH or −NOPATCH	No longer used
−BREAK or −NOBREAK	-nobreak causes program to ignore SIGINT, -break (default) causes program to terminate on SIGINT
−STRIP or −NOSTRIP	-strip (default except for debug versions) removes symbols and shrinks comment section. -nostrip prevents debug and comment section from being removed from executable

The following options (intended mainly for internal use) apply to "source" files only:

−DP4	Tag as a DP4 file by adding a DP4 version stamp, which means that PROGDATE can be run against it
−COMMENT "text"	Allow the insertion of a comment (up to 32 characters) for files such as .C .OBJ .LIB .SYS .BAT