OPCS(OPCS)		Optical Printer Control System		OPCS(OPCS)

	opcs - optical printer control system

    	opcs [startup file] 		# start the OPCS software. Loads
					# 'OPCSDEFS.OPC' from the current
					# directory if [startup file] is not
					# supplied.

        The OPCS software takes commands the operator enters, and executes
	printer operations. The software comes up with a counter display,
	leaving a window below for the user to enter commands. The heart of
	the software is the stepper motor driver routine which can control
	4 axes per up to 3 parallel ports on the back of the computer.

	If executed with no arguments, OPCS will come up loading the file
	OPCSDEFS.OPC in the current directory. This file contains special
	'OPCSDEFS' commands that setup the initial default values for the 
	software. These values can be customized for different sites. It 
	is advised you refer to the man pages for a list of these commands
	via 'man -k OPCSDEFS:' which will list all the commands for you, or
	refer to the OPCSDEFS.OPC file itself, and 'pick up' the commands
	by the 'monkey see, monkey do' approach.
	When starting the software, if an argument is supplied, you can 
	change the name and directory of the startup file:

		opcs \usr\opcs\8perf\startup8.opc

	..which will totally ignore the OPCSDEFS.OPC file on startup, and
	load '\usr\opcs\8perf\startup8.opc' in its place. The above command
	can be put into a batch file to simplify startup for the printer 

	Use man -k opcs to get a list of all OPCS related documentation,
	or man -k opcs: for just the OPCS commands themselves. The same
	goes for man -k opcsdefs:, which will list just the OPCSDEFS
	commands that are avaiable. From the print out of these commands, you
	can determine which commands to pull up a full man page on. Just type
	'man' followed by the name of the command you want to know more about:

	    man cam       # find out more about the CAM(OPCS) command

	Using this technique, you can guide yourself through the use
	of the OPCS commands, and how they inter-relate with one another.

	All documentation pages follow a similar format. EXAMPLE:

CAM(OPCS)		Optical Printer Control System		CAM(OPCS)
 |   |			|
 |   |			The name of the software package
 |   |
 |   The software or context this command is related to.
 Name of the command being documented.

 	The above shows an example of a documentation page's header.
	The name in ()'s is the context of the documentation. Often there
	are commands with the same name that can appear in different contexts.
	One such command is the SPD command, which currently has two 
	contexts; SPD(OPCS) and SPD(OPCSDEFS). SPD(OPCS) refers to the
	command users normally enter to the OPCS software to change the
	exposure speed. SPD(OPCSDEFS) refers to a different command that
	appears in OPCSDEFS.OPC files. Both documentation entries will be
	displayed when you invoke man spd.

    NAME - This usually repeats the name of the command followed
        by a one line description of the command.

    USAGE - This usually shows a syntactical representation of how
        to use the command.

    EXAMPLES - Often literal examples are shown for commands that
        may have a complex syntax. Throughout the MAN pages, literal examples
	are usually in bold or underlined type.

    DESCRIPTION - Usually a few paragraphs, often accompanied by
        examples describe the command and its functions.

    FILES - If any files are of particular relavance to the command
        being documented, they are listed here.

    SEE ALSO - This refers you to related commands, which you can
        bring up with MAN.

    BUGS - If there are known bugs or 'gotchyas' with a command,
        they are listed here. These entries can be very helpful to avoid
	problems you may run into later.

				o   o   o

        Documentation pages are managed by the MAN command, and texts may 
	be customized by the end users if they wish. See MAN(DOSUNIX) for
	more on the technical specifics of how the MAN system operates by
	executing man man.

	For additional help on how to formulate commands, and shortcuts for 
	typing commands, refer to man pages SYNTAX(DOCS) and MATH(DOCS), which
	describes the online calculator, command stacking, and other shortcuts.

        \USR\BIN\OPCS.EXE	- the executable program
        OPCSDEFS.OPC       - the 'start up' definition file
        *.OPC              - other opcs definition files
        *.RUN              - run script or 'LOG(OPCS) scripts'
        \USR\CATMAN\*      - online documentation pages
        \USR\BIN\MAN.EXE	- online documentation program

	OPCSSETUP     - OPCS setup/installation procedures
	OPCSHARDWARE  - OPCS hardware specifics (wiring, etc)
	VERSIONS      - OPCS version information (a list of all revs)
        man -k OPCSDEFS:   - list all OPCSDEFS file commands

	Gregory Ercolano, Los Feliz California 01/18/91
© Copyright 1997 Greg Ercolano. All rights reserved.