Troubleshooting PARIS by Error and Error Code


Got an error message staring you in the face on your PARIS computer right now, with unsaved critical work at risk in an open project? BEFORE YOU DO ANYTHING ELSE, try this: alt-tab to the Project Window, ctrl-shift-S to save your project under a new name.

Feel free to add to the list, or insert additional observations or corrections to specific entries.

IMPORTANT NOTE: This list of "bug" reports relates to both stock installations of PARIS and installations with new drivers. Some are relevant to issues in the application, some upon closer inspection have been traced to driver issues (and in many cases fixed or lessened), and some are OS issues (for example, the "TptQue2 too many files open" issue on Mac OS before 9 - not a bug, just a limitation of the OS) or even simple ErrorEffOhOhEight user errors. It doesn't matter - if they can pop up and mess with your workflow, they're in here. The bugs marked with a red asterisk (*) have now been resolved by MikeAudet Mike Audet's new drivers, which are available for purchase at a modest fee at his website.

Putting PARIS PC in debug mode on initialization


PARIS can generate a text file of debug information that can be extremely useful in troubleshooting.

  1. Right click on PARIS app icon to get menu
  1. Click with left button on open, but don't let go
  1. Hold down control and alt
  1. Let go (launch)
  1. Keep holding alt/control until you see the window at the bottom of the screen
  1. After you reproduce the problem, quit PARIS
  1. Look for a newly created text file named "AppMessages.txt" in the PARIS application folder
  1. Open and read in any text editor

- contributed by Aaron Allen

The "Known Bug" Codex

The Error Code Compendium Project


An initiative to compile all reported PARIS error codes, their causes, and (where possible) their workarounds



PARIS Hardware Maintenance - A Guide to the Do-It-Yourself-er



Back to HomePage
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki