Please enable JavaScript to view this site.

CopiaFacts™ Reference Manual

Navigation: Appendices

Appendix H: File Extensions

Scroll Prev Top Next More

The notes below explain the file-naming conventions and file extensions used by CopiaFacts.

All CopiaFacts programs support long filenames but in some cases filenames are truncated in logs or reports. To use a filename with embedded blanks in a CopiaFacts command file, surround the pathname with double-quotes.

The extensions and names in the following list are either treated specially by CopiaFacts or are conventionally used for a specific purpose:

.001 - .999Formerly used for backup files.  See Backup Files below.
.1, .2, etc May be used for successive pages of a document image when no multiple-page-per-file format is available. The file extensions have no leading zeros. This convention is deprecated and if possible .TIF file extensions should be used instead.
.ALGConventionally used for an algorithm file for the multisegment phrase-speaking feature.
.ASC Causes a document file to be processed as a text file.
.BAK, .BKnUsed for backup files.  See Backup Files below.
.CFG Required extension for the CopiaFacts Configuration File.
.CopiaKeyContains the license portion of a Hardware and License (HWL) file, and is issued to update a CopiaFacts license with new features or maintenance date.
.CVR Causes a document file to be processed as a text file.
.DBF Required extension for dBASE data files. When the filename portion is a date of the form YYYYMMDD or YYMMDD, the file is the CopiaFacts daily log file.
.FS 'Fax' Send files, generated by CopiaFacts for fax-on-demand requests, broadcasts, and client outbound operations. Required extension for externally-generated broadcasts and outbound fax, poll, e-mail and voice operations. You must ensure that the filename portion is unique at all times when CopiaFacts is processing these files. Long filenames of any valid length are supported, but only the last 14 characters of the filename part are displayed on the status screen and reported in the log.  
.FST Used for FS template files.
.FS? Extensions starting with .FS are reserved for future use by CopiaFacts.
.FT0, .FT1 etc. Generated by CopiaFacts for the daily-cycled trace files enabled with the 'trace to file' setting in the FFTRACE program. The filename part is normally the node name, but may also include the application name for service applications. The FFTRACE program receives trace and debug messages from CopiaFacts programs other than the main engine.
.GCT Identifies a Graphical Customization Template file for a faxable TIF document or cover sheet template.
.GPT Identifies a Graphical Customization Template file for a PDF document or cover sheet template.
.GTT Identifies a TIFF file in which the contents of a Graphical Customization Template are embedded in a spare tag. The 'watermark' file is the enclosing TIFF file.
.GW0, .GW1 etc. Generated by CopiaFacts for the daily-cycled Gateway trace files enabled with the 'Trace' checkboxes in GWMANAGER.
.HWL CopiaFacts hardware and license control file controlled by CFHWL.
.IIF Required extension for CopiaFacts Infobox files.
.IPK Causes a document file to be processed as a Brooktrout Infopkt file. Generated by CopiaFacts for Brooktrout cover sheets.
.JCF Job control file containing a list of the FS file names (without path) comprising the job instance. No longer used by default in CopiaFacts V8 and later.
.JCX Job control file containing a list of the FS file names (without path) for any Proof or Report transmissions associated with a job instance. No longer used by default in CopiaFacts V8 or later.
.JPF Job control file containing a list of the FS file names (without path) associated with internal worker box operations for a job instance. No longer used by default in CopiaFacts V8 and later.
.JST Job status file containing just the numeric value of the status of the job instance (see Appendix J).
.LNSChannel schedule for a COPIAFACTS node.
.LST Causes a document file to be processed as a text file, normally with fields separated by the Windows delimiter character (in the USA: a comma), for FFBC and JOBADMIN.
.MBX Required extension for faxmail mailbox files. The filename portion must be numeric, with leading zeros.
.MBXT Used for mailbox template files.
.MCF Generated by CopiaFacts for fax received and for the 'accept' channel operation. The filename portion must be numeric, with leading zeros, except that the first character of the filename may be changed to 'P' to indicate that the document has been printed.
.MIFContains "envelope" information about e-mail received by the CopiaFacts SMTP Gateway.
.MSGUsed for the content of an e-mail received by the CopiaFacts SMTP Gateway.
.MSG Generated by CopiaFacts for voice messages recorded by callers in a format other than .WAV. The filename part is the call number. No supported voice interface saves voice messages in this format.
.NDX Required extension for dBASE index files.
.OMA Generated by CopiaFacts for the Operations Monitor Alert file written every 15 seconds. Enabled with the OMA option in the COPIAFACTS, FFEXTERN and CFGATEWAY programs, and optionally by others, and monitored by OMACHECK. The filename part is normally the node name.
.OMXA data file generated with a reason code when OMA updating is suspended.
.SMR Conventionally used for Smart Retry override parameter files.
.SUM Text file containing the summary totals of the sent/failed/retried items in a job instance.
.TAB Tab-separated-fields in a file used for Job broadcast lists or result data extracted for a job instance.
.TFS Temporary extension used while a .FS file is actually being written, to prevent an incomplete file from being accessed. Formerly a temporary extension of .$$$ was used, but some virus-checkers were unable to exclude such files.
.TIF Conventionally used for TIFF/F document files. Such files can also be recognized when they have other file extensions.
.TR0, .TR1 etc. Generated by CopiaFacts for the daily-cycled trace files enabled with the 'trace to file' setting in the COPIAFACTS program. The filename part is the node name.
.TLS Causes a document file to be processed as a text file, normally with tab-separated fields for FFBC and JOBADMIN.
.TSPTOSEND queues priority schedule for a COPIAFACTS node.
.TSSTOSEND queues schedule for a COPIAFACTS node.
.TXT Causes a document file to be processed as a text file. When specified as a broadcast list file it is assumed to have tab-separated fields for FFBC and JOBADMIN.
.UJP Job properties file. May be 'system', 'owner', 'jobtype' or 'job instance' properties. This file contains a superset of the user profile commands.  
.UJPT Used for user properties template files.
.USR Conventionally used for CopiaFacts user profiles.  
.USRT Used for user template files.
.VOX Optional extension for image description files which are found automatically along with the document files. Other extensions can be used if explicitly specified as an image description. Extension for Standard Voice Prompt messages SVPn.VOX. This format is now rarely used.
.WAV Optional extension for image description files which are found automatically along with the document files. Extension for Standard Voice Prompt messages SVPn.WAV. If both .WAV and .VOX are present, only the former is used. See also the entry in the Features section describing the use of WAV files.
.XLS, XLSX Excel worksheet used for FFBC or JOBADMIN broadcast list.
00000000.* Reserved for the prefax document. The file extension depends on the file type.
99999999.* Reserved for the suffax document. The file extension depends on the file type.
FAXMSG.* Former required filename for system messages, with numeric extension corresponding to the system message number (without leading zeros). Now superseded by SVPn.VOX or SVPn.WAV.
Image Files The filename portion of fax-on-demand document image files, infoboxes, and voice description files must either be entirely numeric (with leading zeros making an eight-digit filename) or alphanumeric with from 1 to 8 characters. Alphanumeric filenames cannot be selected directly by a fax-on-demand caller, but can be selected indirectly using infobox commands.

Windows File Associations

From version 8.3.0.214, CopiaFacts follows current Windows guidelines and no longer attempts to set a CopiaFacts application as the default file association for a file extension. Instead it specifies the file extensions that each application can handle, and allows the user to select that the application should be the default ('Always use this app to open .... files').

The installer always configures the file extensions supported by each application, and the option to set the application as the default has been removed from the installers.  The extensions are as follows:

FFVIEWER.TIF .GCT .GTT .GPT
FFPLAY.WAV
COPIAEDIT.CFG .USR .USRT .UJP .UJPT .FS .FST .MBX .MBXT .IIF
TRCVIEW.TRx .FTx .GWx   (x=0..6)
CFHWL.CopiaKey

Backup Files

Earlier versions of CopiaFacts used three-digit extensions for backup files: .001 to .999.  This has resulted in large numbers of unnecessary files being retained.  From build 8.3, the following file backup extensions are used:

Command filesA single backup is made when the file is saved from COPIAEDIT, by adding a tilde in front of the file extension.  So the backup file of FAX.USR becomes FAX.~USR.
All other filesWhere necessary, up to 10 backup files are created. The newest file is always .BAK, and then .BK1 up to .BK9 are used, with each file being renamed to the next highest number. When there are 10 backup files in existence, the next save of the file to be backup will cause the tenth backup file, .BK9, to be lost.

The files currently backed up using the .BAK, .BKn mechanism are:

FAXFACTS.CFGThe main configuration file is backed up before editing by SERCONF, EMSETUP and OTFCONFIG.
FAX.USRThe default user file is backed up before editing by SERCONF.
FAXCOUNT.HWLThe hardware and license file is backed up before editing in CFHWL.
Do Not Send FileAn NDX file is backed up before the Recover and the ReIndex operations in the CFUTIL CFUTIL PIN program.
USR/MBX FilesThese files are backed up before editing in the Client Administrator program CFCLIENTADMIN.

When edited by non-Copia programs, a different renaming strategy may be applied to the above files.