JAGUAR PRO ONLY

Software support is available only for JAGUAR PRO users. Most JAGUAR production versions are very stable while the TEST versions may have issues due to a fast development cycle. If JAGUAR crashes unattended, no problem: JAGUAR has been developed for an unattended 24x7 use so LIFESAVER.EXE will normally wake up JAGUAR again and no recordings will be lost.

When you report an issue to groups.io, it will be fixed asap - just help the development team by giving a "recipe", or detailed instructions how to reproduce the problem. We cannot fix the problem without adequate details so please don't send bug reports just mentioning "Jaguar crashed last night" or "xxx failed". If we cannot reproduce the issue based on your description, we will ask for more information and/or start a detailed debugging process.

If you have any issues at JAGUAR start-up, most likely the culprit is located in the SYSTEM.INI file. You can try TOOLBAR > SHUTDOWN > RESET which deletes SYSTEM.INI and/or SETUP.INI and restarts JAGUAR. An alternative way is to delete SYSTEM.INI and SETUP.INI files manually from the Jaguar folder. JAGUAR will deploy all the default settings at the next start-up. If nothing else seems to help, you may also try to make a fresh install from the JAGUAR full-installation package.

Also, if you are running an old version, you should try installing the latest version (via STAR EXPESS) before reporting any bug or issue. It is possible that the issue has already been fixed.

Sometimes the culprit may be in the Windows operating system itself. For example, users should enable the Windows cache flushing if external hard disks are used, and disable all sleep states in Power Settings as dscribed in the installation instructions.

When a severe error/crash happens, Jaguar writes a line into LIFESAVER.LOG. This log is saved in the Jaguar folder. One common log entry is HANG. This means that the I/O flow from Perseus to the buffer disk is interrupted, and it cannot be recovered automatically without a JAGUAR restart. If your LIFESAVER.LOG contains a lot of these entries, changing a USB port or the USB cable may help. Note that in a 24x7 operation, there may be a few such HANGs weekly also in "100% healthy" setups.

HOW TO

* CRASH / HANG / WRITE messages can contain a reson code (#00000000-#99999999) in LIFESAVER.LOG. If you find several CRASHES / HANG lines with the same reason code, please provide that code as part of the bug message. Currently known issues (no need to report these) are

WRITE #00000000 = Writing Perseus data stream to disk fails, zero bytes written
CRASH #40000000 = Perseus input buffer reference fails

In "Zero bytes written" case we could continue operation, but Jaguar decides to bring the services down and ask Jaguar restart from LIFESAVER.EXE, without doing this the currently running recording(s) would be lost. After this forced restart the current recording continues normally.

* You can test how your setup survives from unattended crashes by creating an artificial crash during recording: type

.CRASH

(dot before CRASH) end press enter and see if Jaguar is automatically recovered and if the recording continues normally after that (artificial) crash.