Unsanity, LLC is dedicated to providing quality support. Please read our FAQ before emailing us to streamline the process.
Lost Registration Information
If you have lost your registration information, enter the e-mail you used when registering, and all the needed information will be sent to you immediately.
Product Support
Select a product from the list to view the Frequently Asked Questions for it:
Or, select a category of FAQs to view:
General • Software Products • Purchasing & Orders
Frequently Asked Questions
Top Questions for Support Is Smart Crash Reports a System Extension?No, none of our products are system extensions. In fact, the term "system extension" only applies to Mac OS 9 and was used to refer to software products that patch "traps" in the Mac OS. These extensions affected all processes and all users (not that Mac OS 9 had complete multiple user support). Most of them were drivers or other very low level items. A few others granted some extra features. Since they were system wide, it was not possible to isolate them to a particular process or user and a simple bug in one would take down the entire system. Kernel Extensions (KEXTs) are most analogous to system extensions in the days of yore. Apple's documentation for KEXTs begins with reasons you should not use them. None of our products use or install KEXTs.
Smart Crash Reports works by affecting one process, the Crash Reporter (located at /System/Library/CoreServices/CrashReporter.app) which is launched only when an application crashes. SCR does nothing to any other process. It also needs no direct support from an SCR enabled application to work. This is why the minimum addition to enable Smart Crash Reports in an application is two new entries inside a text file included with every Mac OS X application.
However, due to a limitation in the Apple created mechanism SCR uses, InputManagers, Smart Crash Reports will appear in the crash logs of all Cocoa applications. See this support entry for more information.