The names of the various configuration files depends on the version and release of DP4 installed. Different releases of DP4 also have varying degrees of flexibility as to the location of these files, and there are significant changes in the DP4 Enterprise release.
The changes in DP4 Enterprise (4.620 or later) have been made for three reasons:
The name and location of the DP4 configuration file is dependent on the operating system.
On Windows platforms there must be a DP4 configuration file in the same directory as syslibt.dll (or syslibce.dll on Windows CE), and it must be named dp4.ini. If for the time being you wish to continue to name the "real" DP4 configuration file datafit.ini and to store it in the Windows directory then dp4.ini must contain the following two lines only:
[branding]If you do this make sure any other new entries you want to add to the DP4 configuration file are added to datafit.ini, not to the new dp4.ini.
Do not add the line dp4.ini=dp4.ini to dp4.ini. This would cause dp4.ini to be located in the Windows directory and hence to potentially clash with other dp4 installations. If you want to store dp4.ini in some other directory than the directory that contains syslibt.dll make sure you specify a full pathname. Do not use relative path names, because the working directory for a program may not always be what you expect.
If dp4.ini does not have a definition for dp4.ini then dp4.ini in the directory containing the loaded syslibt.dll/syslibce.dll is used for all DP4 configuration file information.
On other platforms, in particular on Unix and Linux, there is no reliable method of discovering the location of a currently executing binary component, and it is therefore not possible to determine a location for dp4.ini as for Windows. Instead dp4.ini is located as follows: if DP4HOME is defined in the environment its value is assumed to point to dp4.ini, otherwise if the current working directory contains dp4.ini then this is assumed to be the correct dp4.ini, otherwise dp4.ini is assumed to reside in /usr/dp4. To maintain compatibility with existing Unix installations of DP4 in /usr/datafit define DP4HOME=/usr/datafit/ in the environment before loading DP4 components. This initial dp4.ini can be redirected as on Windows, (except that where there is no path component in the name the current working directory is assumed) but there is no reason to do so as datafit.ini was not used in earlier releases.
For compatibility purposes and for the release 4.620 only the licence file may continue to be called datafit.sys. dp4.sys will be used in preference to datafit.sys if both files exist. The two files are currently identical in format, and datafit.sys can just be renamed to dp4.sys. It is probable that some additional information will be added to the added to the end of dp4.sys in future. Only a few DP4 core components access this file by name, so switching to the new name should not cause any problems.
The name and location of the userdata.sys file is described below.
The DP4 configuration file is called datafit.ini The file is only used in the Windows version of DP4, and must be installed in the "Windows" directory. Depending on the version of Windows this directory is given either by the windir environment variable, or the SYSTEMROOT environment variable.
The DP4 licence file is called datafit.sys. On Unix/Linux the file must reside in /usr/datafit, on other operating systems the file resides in the location given by the DATAFIT environment variable. If this variable is not defined the "current" directory is assumed, or for older versions of DP4 the "root" directory.
The name and location of the userdata.sys file is described below.