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 Will your applications be compatible with Mac OS X 10.6?We offer complete refunds up to 30 days after the purchase date.
We may refuse a complete refund request (or offer a partial refund only) if the problem that prompted the refund could have occurred before you purchased the software (such as cannot download the software, a problem that occurs within 10 minutes of using it (we offer 15 day trials), or you are running Microsoft Windows)
So please, please download the trial software and make sure it does what you want it to do before purchasing it.
Finally, log out and then log back in to complete the process.
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.
- init
{
if (self=[super init])
{
NSString* bundleID = [[NSBundle mainBundle] bundleIdentifier];
if (bundleID && [bundleID isEqualToString:@"com.apple.CrashReporter"])
{
SInt32 sysVers;
if (Gestalt(gestaltSystemVersion, &sysVers) == noErr &&
sysVers >= 0x1040 && sysVers < 0x1050)
{
// initialize SCR for CrashReporter
}
}
}
return self;
}
Giving developers access to those logs helps them track down bugs faster and easier in their apps, just as it helps Apple to find bugs in their applications and OS X, which is a win for users. If did not send the crash logs onto Apple as well, it may end up reversing the situation instead of improving it. If crash reports were not sent to Apple, there is the potential for bugs and problems becoming harder for Apple to find and fix. While we can understand why developers might want this, we have decided to err on the side of caution because we fear Apple not receiving reports could harm users in the long run.