Filter
Top Products
MERLIN LEGEND Communications System Release 6.0
System Programming
555-660-111
Issue 1
February 1998
Programming with SPM
Page 2-27Using SPM
2
Backup 2
The Backup procedure is used by qualified service personnel to create a file of
system programming information either in the \spm\backup directory (on the hard
drive of the PC) or in the root directory of a diskette (on the floppy disk drive of the
PC).
NOTE:NOTE:NOTE:
Back up your system programming information on a regular basis. A current
backup file allows you to quickly and easily restore your system, if the need
arises.
Determining the Release Number
of a Backup File 2
If you have a backup diskette but do not know its release number, you may be
able to find this information in the backup header. Beginning with later versions of
Release 1.1, the backup file contains a backup header 128 bytes long.
Approximately 59 of these bytes are currently used. Bytes 55 through 59 of the
header contain the MERLIN Legend Communication System Release number, as
shown in Table 2–4
. (Release 1.0 and early versions of Release 1.1 do not
contain this information in readable form.)
The release number is found in the first two bytes (four characters) of the
identification number. For example, 0300 = 3.0, 0201 = 2.1.
If the backup file is compressed, you can read the header but you cannot read the
data area following the header. Use
[
backup filename
] to read the header on
a DOS system or
[backup
filename
] to read the header on a UNIX System.
Note that the communication system release number, not the version number of
SPM, reflects whether the backup file is compressed or uncompressed.
Release 1.0 backups are uncompressed and Release 1.1 and later backups are
compressed. Uncompressed files take longer to restore.
Table 2–4. Backup Header: Release Number
Release No. Build No. System Size Mode
Size 2 bytes 12 bytes 1 byte 1 byte
Examples 03 00 32 01 01 - Key
02 01 02 - Behind Switch
03 - Hybrid/PBX