This can be caused by two things:

• You have inadvertantly turned off the disk output. Thsi can happen a number of ways, including by jamming up the network lines by trying to move your (very large) data files across the network while observing.
  

  To fix, just type "disc on". Then type "disk status" to be sure that you were successful.

• The disk is full. This should happen, but it does. To see if this is your problem, go to some other window on observer and type "df -k /export/obs8". If the capacity is listed as 100%, you have a problem.
  

  To fix, first double (and triple) check that this is your problem. Once you are convinced it is, you need to get someone from the computer department to help you out. Ask the operator to contact someone for you.

This is caused by the fact that you (hopefully) installed everything into your project directory as dtusr while the datataking system, which needs to write to the logfile, is actually "vxw".

To fix, just go into the Sunos window and change the mode of your log file so that anyone can write to it. That is, type:

This may be caused by you having typed either a square or curly bracket ([ or {) on the datataking window. You can do this without realizing it through a combination of the control key and other characters.

To fix, just type a whole bunch of closing square brackets (]]]]), hit return, and then hit a bunch of closing curly brackets (}}}}})

This is probably caused by random network problems.

To fix, try just exiting the datataking program and restarting it. (Don't forget to move your data first!). If that doesn't work, try logging out of observer (again after moving your data and then exiting vxWorks) and restarting. If you try both of these things a few times and nothing's working, have the operator take a look at the correlator for you and make sure nothing's wrong. As a last resort, exit out of observer and have the operator reboot the correlator.

This may be caused by the pointing tolerance being set too high. Look in the upper right corner of the pointing monitor window. The variable "tolA" should be set to 10.0. If it isn't, this is your problem.

To fix, go into the "datataking" window and type "pnt tol 10.0" to reset the pointing tolerance to 10 seconds.

This may be caused by the power meter being turned off.

To turn it back on, ask the operator or, in the vxworks window, type "acpwrm on". You can also turn the multimeter on by typing "accm on". You probably need to exit the data taking program after you do this. If both meters are on, the if/lo window (on the console next to the observer console) should read "ac1Sw:0", "ac2Sw:3"