Article Title           : NCD panic
Creation Date           : unknown
Author                  : unknown
Last Update             : 8-15-95
Last Update By          : NCD Technical Support
Expiration Rules        : 
Location		: NCD-Articles/NCDware
=============================================================================

                   What To Do If An NCD Panics
                   ===========================

1. Record  the following  information 

   -- NCDware Server Version.
   -- Boot Monitor Version.
   -- How much memory is installed in the NCD.
   -- Type of network option card and flash card if there is one.

2. Record  what you  were doing/running on  the NCD at  the time  of the
Panic. Specifically, record the window manager you were using, and the types
and numbers of each client, including local terminal clients.

3. Answer the following questions:

   -- How many panics have you seen on this terminal?
   -- Have any other terminals panicked?
   -- Can you reproduce the panic?
   -- Could this be a hardware problem?

4. All of the above information is needed to help us diagnose the
   cause of the panic. Identifying the cause can be very difficult
   for some types of panics. Reproducing the panic can be key to 
   identifying the problem, but of course the panics which are hardest
   to identify are the ones which can't be reproduced.

   If we can't identify the problem from the above information, we 
   will ask for a 'dump' from the panicked terminal. Use the following
   steps to get a dump. Do not e-mail the dump to us. We will arrange
   to get the file from you.

5. For HMX terminal, please put the following line in the terminal's
   remote configuration file, reboot it, before panicking the terminal and 
   getting a dump file:

	diag-severe-system-errors = abort

   Please be sure to set it back to:

	diag-severe-system-errors = warn 

   ...as after you have been able to get the upload.
 
At  the NCD's ">" prompt:  use the "UP" command to upload the contents
of memory to your host.  The "UP" command is the reverse of the "BT" command
in that it uses TFTP to upload the contents of memory to a file on the host.
The file on the host must exist, it must be world writeable and it must end
in ".dump", eg "ncdunit.dump". If you are using secure tftp, the file
must be in the secure directory. This file can be very large, as large
as the amount of memory in the terminal. Be sure that you have enough
disk space.

After you have created the file and given it write permission, use
the following command to do the upload.

> UP file <ip of ncd> <ip of host> 

Notice you do not put the ".dump" suffix on the file name.

If successful you will see "......" across the screen just like at boot time.
If you do not have enough disk space available, you can interrupt the
upload by pressing "Escape".  Sometimes an incomplete upload can still
help, so save the dump if you can't get a complete one.

After the upload is successful, contact NCD X Terminal software 
support and report the problem. Do not e-mail the dump to us. We 
will make arrangements with you to get it after you have contacted 
us.

Network Computing Devices X Terminal Technical Support
---------------------------------------------------------------
E-mail: support@ncd.com
Phone: (415) 691-7445			Anon ftp: ftp.ncd.com
Fax:   (415) 961-7774			URL: http://www.ncd.com
---------------------------------------------------------------