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 Products Will your applications be compatible with Mac OS X 10.6?Prior to version 2.0:
Click on APE Manager or Application Enhancer in System Preferences. Choose the Uninstall option under the Information tab.
Version 2.0 and newer:
Click on Application Enhancer in System Preferences. Click the "Troubleshooting..." button in the About tab. Click the "Uninstall Application Enhancer..." button and follow the instructions.
OR
Download the Application Enhancer installer from unsanity.com/haxies/ape run it and click uninstall.
To fix it, open the Appearance Preference Pane (Apple Menu->System Preferences, then click Appearance) and make sure that "Minimize when double clicking a window title bar" is checked.
Also, please make sure that WindowShade X is enabled in both the WindowShade X pane and the APE manager pane of System Preferences.
1. Open Console in Applications/Utilities/Console
2. Open the Console Preferences.
3. Click "Crashes" and check both boxes.
4. When a crash happens, Console will open and you can then select the crashlog text. Alternately you can find the file in your ~/Library/Logs/CrashReporter/ folder.
Under Mac OS X 10.3 Panther and Mac OS X 10.4 Tiger:
1. Open Console from Applications/Utilities/Console
2. Click the "Logs" button in the toolbar to show the Logs sidebar.
3. Expand the "~/Library/Logs" and subsequently the "CrashReporter" sections and select the corresponding file.
4. In the File menu select "Save a copy as...".
Email the crashlog and details about the crash to support@unsanity.com
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;
}
Delete the file from the following location:
~/Library/Caches/com.apple.preferencepanes.cache (the tilde (~) means your Home directory)