Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ diag(1SPP) — mips UMIPS RISC/os 5.01

Media Vault

Software Library

Restoration Projects

Artifacts Sought



DIAG(1SPP)          RISC/os Reference Manual           DIAG(1SPP)



NAME
     diag - diagnostic script execution program

SYNOPSIS
     diag [ catalog ]

DESCRIPTION
     Diag is an example of a standalone program written with the
     standalone library.  Diag reads a catalog of standalone pro-
     grams to be run, and executes each of the programs listed
     with the arguments indicated in the catalog.  Diag is used
     at MIPS to run a series of diagnostics, hence the name diag.

     Diag is normally placed in the bfsd(8spp) home directory on
     some UMIPS-BSD server.  Standalone systems attached to an
     ethernet may then run diag with the prom monitor command:
          boot -f bfs()diag catalogfile

     Once running, diag prepends "bfs()" before the catalogfile
     and reads this file via the ethernet and bfsd(8spp).  If
     catalogfile is not specified, the file "bfs()catalog" is
     read.

     Catalogfile should be a list of commands and their argu-
     ments.  Each command in the list is prepended with "bfs()"
     and then booted with the arguments that appear on in the
     catalogfile.

     An example catalog might be:
     test1 arg1
     test2 arg2

     Given this catalog file diag would first boot "bfs()test1"
     with the argument "arg1", after test1 completes diag would
     the boot "bfs()test2" with the argument "arg2".

BUGS
     Diag must not be overlayed by the programs it loads, since
     these programs return control to diag.  At MIPS, we load
     diag at 0xa0020000, we load the diagnostics run by diag at
     0xa0100000.  Diag starts the diagnostic program's stack
     beneath its stack.













                         Printed 1/6/92                    Page 1



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026