User's Manual

PERFORMING DOWNLOADS
Effect of Downloads on Existing Files and Data
118 VX 675 REFERENCE GUIDE
Direct Application
Downloads
This section provides the hardware and software checklist needed for direct
application downloads. The procedure for direct application downloads is also
discussed.
Hardware Checklist
Software Checklist
Checklist for Effects
on Files and
Settings in the
Receiving Terminal

The correct cable connects the download computer serial port (COM1 or COM2)
to the RS-232 serial port (COM1) of the VX 675 terminal.

Download Manager, VeriCentre, or DDL.EXE running on the host computer.

The application file to download (full or partial) is located on the host computer.

The correct keyed record variables exist in the CONFIG.SYS file(s) of the file
group(s) to store the application files.

Certificate files (*.crt) required for file authentication on the receiving terminal
are stored in memory or they are located on the host computer, and must
download with the application files.

All required signature files (*.p7s) generated using FILESIGN.EXE are located
on the host computer. One signature file downloads for each executable (*.out
or *.lib) to run on the terminal.

The filenames in the batch download list on the host computer indicate which
application files to redirect to
F: drive and file groups other than the target group.

Ensure that filenames and CONFIG.SYS variables to download are correct in
relation to those stored in the memory of the receiving terminal to avoid accidental
overwrites.

The required Verix Terminal Manager and file group passwords are available to
make the required Verix Terminal Manager menu selections and to prepare the
receiving terminal to receive the application download.

Protected records in the CONFIG.SYS file(s) of the receiving terminal — keyed
records that begin with * or # — are not erased.

The bootloader, OS, and other firmware on the receiving terminal are not modified
as a result of the application download.

The certificate tree that exists on the receiving terminal is not modified unless one
or more new certificate files are downloading to the terminal. When new
certificates are authenticated on the receiving terminal, the data they contain is
stored in the certificate tree and the certificate files are deleted from the
I: drive of
the target group.