Support Navigation:
The following file naming convention standards are effective as of July 1, 2005.

Update Information
Update files may consist of one or more files to download per platform. If an update requires two files, you will need to download both to have the entire update.

How to Decide
Choose the COMPLETE VERSION if you have never installed this product before or if your version is more than one release behind the current offering. Choose the UPDATE version(s) if you are updating the last release only.

Self-extracting or Self-installing EXE?
After you have decided between COMPLETE and UPDATE, you must select the file format. You may choose either the self-extracting or self-installing format. When you run the self-extracting file it automatically extracts the compressed files. The self-installing file automatically extracts the compressed files and then begins the installation procedure; this file can be identified by the "I" in its name. For example, "CE01ICE1.EXE"

File Naming Convention

Product file names will be made up of 8 sections:

The filename will look like this: "PDmmMRL#.xxx"

Where:
1. PD = 2 character Platform Description

Note: The platforms designated (*) became effective with the CSAV v4.70 release.

*Windows 32 Bit Platforms (9X/ME/XP, NT, 2000) - Home User/Small Business Version cs
*Windows 32 Bit Platforms (9X/ME/XP, NT, 2000) - Enterprise Version ce
Windows 9x/ME 9x
NT Workstation nt
NT Server ns
2000 Professional 2k
2000 Server 2s
Microsoft XP xp
Novell Netware nw
Netmail nm
Exchange (MAPI) em
Exchange (Microsoft API) ea
Exchange (2000) e2
Lotus 4 l4
Lotus 5 l5
Gordano gd
CSSCentral cc
*COMMANDCentral cm
COD Biz Dev Version c1
COD Commercial Version c2
COD Virus.com Version c3
Plugin for WEBsweeper 4.0 wb
Plugin for MAILsweeper 4.2 m3
Plugin for MAILsweeper 4.1 m2
Plugin for MAILsweeper 4.0 m1
Plugin for MIMEsweeper 3.2 mm
Interceptor for GWAVA ig
Outlook Scanner sc
Multiplatform (used for multiple platform builds) mp

2. y = 1 digit Year designation
2003 3
2004 4
2005 5
2006 6

3. m = 1 digit Month designation
January 1
February 2
March 3
...September 9
October a
November b
December c

4. M = Method of Compression/Deployment
Self-Extracting e
Self-Installing i
Single Folder s
Package p
ZIP z
RPM r
TGZ t

5. R = Release Type
Patch or Component p
Commercial c
Beta b
EVAL/Test Drive e
OEM o
Update u

6. L = Language
English: US e
Spanish: Castilian h
Spanish: LatAm s
French f
German g
Portuguese p
Swedish w
Chinese-Simplified m
Chinese-TW x
Thai t
Arabic a

7. # = Number of same Platform Builds in a Month
First Build 1
Second Build 2
.. through 9th Build 9
10th Build a
11th Build b
.. through 15th Build f

One "hexadecimal" character designating the number of same platform builds in a month in sequential order. (1 being the first build created that month (skip zero). It is not expected to have more than "F" builds for a single platform in any given month. F hexadecimal is equivalent to 15 decimal.)

For example CE35ECE1.exe would translate to Windows 32 Bit Platform, Enterprise Version, May 2003 build, self extracting, commercial, English build, the first build created in the month. The builds will be archived periodically. The archive will designate the year of the build.

8. .xxx = Filename Extension. Most builds are self-extracting or self-installing files, which are designated as ".exe". Zip files have the extension ".zip".

Definition Files
Definition files are becoming more and more platform specific. Definition files should be named as follows for the following platforms:
# defmsp.exe - Windows 2000 definition files
# defcod.exe - Command on Demand (COD) definition files (all the latest COD def files, rebuilt each time one or more def file changes)
# macro.cab - COD equivalent of macros.def (single update)
# sign.cab - COD equivalent of sign.def (single update)
# sign2.cab - COD equivalent of sign2.def (single update)
# main.cab - will always accompany the above def files, whether one or more change
# deffiles.exe - Windows (except 2000)

bac to top of page