C-4
Initialization Information
CAUTION!
Do not change the second field, which is the symbolic name used by the OM 1000. Changing the name can cause an
initialization failure.
Figure C-1 provides an example of an FOF file:
Figure C-1
Sample FOF file
#----------------------------------------------------------------------------
# OM1000 Software File-Of-Files
#
# FILE INFO:
# $Workfile: om1000.fof $
# $Revision: 1.6 $
# $Date: 04 Jun 2002 09:34:14 $
#
# DESCRIPTION:
# File-of-Files template for factory use.
#
# NOTES:
# This file is read by the OM during the BOOTP process. The OM maintains
# a local copy of this file for comparison with the BOOTP'd file during
# initialization.
#
# The file systems may be case sensitive. The unit file names and paths
# shown below should be in lower case.
#
# The ".fcf" file listed below is for factory configuration ONLY.
# Downloading this file to an OM 1000 other than the one for which the file
# was customized MAY CAUSE THE OM 1000 TO BECOME INOPERATIVE. The ".fcf"
# file entry below should be commented out or removed entirely, except when
# it is desired to download the file during initial OM 1000 configuration.
#
# The om1000.svc, om1000.gtw, om1000.hst, and om1000.ini release files
# are templates that may require setup for a particular installation.
# Although default settings are provided, these files are site specific
# and usually require reconfiguration during headend installation. Refer
# to the installation procedures for further information.
#
# An "F" flag at the end of a line denotes a forced download of the file
# indicated on that line. Without the "F" flag the OM 1000 will first
# check to see if the boot server file path and name already exists on the
# OM 1000. If so, the file will NOT download the file from the BOOTP
# server. An "F" flag is not needed during initial configuration because
# the unit has no files and therefore will download all files.
#
OM 1000 Installation and Operation Manual