Mercurial > hg > Members > kono > nitros9-code
diff docs/nitros9guide/verify.refentry @ 140:35dd8ae53dee
Split up the commands into individual files.
author | roug |
---|---|
date | Sun, 07 Jul 2002 08:58:56 +0000 |
parents | |
children | 9639def8cf2e |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/docs/nitros9guide/verify.refentry Sun Jul 07 08:58:56 2002 +0000 @@ -0,0 +1,59 @@ +<refentry id="verify"> +<refnamediv> +<refname>VERIFY</refname> +<refpurpose>Verify or update module header and CRC</refpurpose> +</refnamediv> + +<refsynopsisdiv> +<cmdsynopsis> +<command>VERIFY</command> +<arg choice="opt"> + <option>u</option> +</arg> +</cmdsynopsis> +</refsynopsisdiv> + +<refsect1><title>Description</title> + +<para> +This command is used to verify that module header parity and CRC +value of one or more modules on a file (standard input) are correct. +Module(s) are read from standard input, and messages will be sent to +the standard error path. +</para> +<para> +If the U (update) option is specified, the module(s) will be copied +to the standard output path with the module's header parity and CRC +values replaced with the computed values. A message will be +displayed to indicate whether or not the module's values matched +those computed by VERIFY. +</para> +<para> +If the option is NOT specified, the module will not be copied to +standard output. VERIFY will only display a message to indicate +whether or not the module's header parity and CRC matched those +which were computed. +</para> +</refsect1> +<refsect1><title>Examples</title> +<screen> +OS9: verify <EDIT >NEWEDIT + +Module's header parity is correct. +Calculated CRC matches module's. + +OS9: verify <myprograml >myprogram2 + +Module's header parity is correct. +CRC does not match. + +OS9: verify <myprogram2 + +Module's header parity is correct. +Calculated CRC matches module's. + +OS9: verify u <module >temp +</screen> +</refsect1> +</refentry> +