8. If things go wrong . . .738. If things go wrong . . .In Laurel, as in most interactive systems, lots of things can go wrong. Also as in most systems,some of them are your fault and some of them are not. Laurel tries to prevent you fromwreaking destruction upon your environment, and reports any (perceived) violations in thefeedback region.The error reports in the feedback region are intended to be self-explanatory. If you cannot figureout what one means or what to do next, please send a message to LaurelSupport.PA (using Laurelif possible).If Laurel detects certain internal error conditions, it interrupts whatever command was in progressand posts a message in the feedback region. In some cases, Laurel may decide that the errorshould be reported to LaurelSupport.PA, and, in such cases, it will prepare an error report form(after confirmation from you). This form contains internal status information of interest to theLaurel implementers and should be used whenever possible. If you confirm the use of this form,Laurel will restart itself and display the form in the composition region. You should then followthe instructions contained within the form, after which Laurel will again be available for normaluse.The vast majority of Laurel internal errors reported in the last year have turned out to be due toproblems with the disk or with the Alto (Dolphin, Dorado) processor. If Laurel "freezes" orotherwise behaves peculiarly for no apparent reason, a simple check of your disk will probably fixthe problem. Run the Scavenger.run program from the Alto Executive. If it reports a "Readerror", then have a hardware maintainer check out your disks thoroughly. If Laurel continues tobehave strangely, e.g., it doesn't run at all, suspect the processor. If you have sent in an errorreport through the built-in error reporting mechanism, and you later discover that the problemreally was due to faulty hardware, then please send a message to LaurelSupport.PA to explainwhat happened."Freezing" is defined as Laurel becoming completely unresponsive to mouse movement andkeyboard input. If the cursor moves when the mouse is moved, then Laurel has not "frozen"; bepatient and wait a bit longer for the current operation to complete. Only if an operation takes avery unreasonable amount of time should you suspect that Laurel is in a bad state. Use yourgood judgment; a long file transfer or a Quit or Mail file command given when the current mailfile has over a hundred messages may take a while. If your cursor does not move when youmove the mouse, but keyboard input is accepted by Laurel, then check to see whether yourmouse is properly connected. (We get them all.)Regardless of the above discussion, when Laurel enters automatic bug reporting mode, a realLaurel bug may be the culprit. Please do fill out the description part, and deliver the error reportmessage. Only because of the diligent attention paid to these error reports by users in the pasthas Laurel has become as error free as it is.#fpXFf g^q gZCpP gXx8 gV7" gT gQqc gO<" gM gJjS gH;! gF;% gE a gC@A gAu*8 g?!@ g= g:nN g8D g6F g5D g3C T g1y] g/:$ g-@ g, g(3# g&$: g%E g#GA g!}(rprp$ g+. g%3 g0 g6% gF gO gK- g