We have seen situations where somehow the configuration file used by the JamKazam application can become corrupted, and this can cause the application to become completely or largely unusable. In this case, deleting the app configuration file can let you get a fresh start, and clear out these problems.
There are two ways to delete the JamKazam application's configuration file - either by using an in-application hotkey to do it for you; or by manually deleting the configuration file through the file system on your computer.
Application HotKey to Delete Configuration and Restart
The easiest way to go is to use a hotkey feature we have built into the application. To use this feature, while the application is running on your computer, press and hold down the three keyboard keys noted below, and you will see a dialog box displayed with a message asking if you are sure you want to delete the configuration file. Click 'yes' to accept, and the file will be deleted.
- Windows: CTRL + SHIFT + D
- Mac: CMD + SHIFT + D
Manually Deleting the Configuration FileIf for some reason you cannot or do not want to use the hotkey feature to delete the configuration file, you can do it manually by navigating through your computer's file system and manually deleting the file. We only recommend this option for power users who are confident in what they are doing.
Where is the configuration file?
* Windows: C:\Users\<User>\AppData\Roaming\JamKazam\Client.ini
* Mac: /Users/<user>/.config/JamKazam/Client.ini
On Windows, the AppData folder is a hidden folder. You can get to it even when it's hidden by doing the following (these steps are a modified version of this: http://www.microsoft.com/security/portal/mmpc/shared/variables.aspx):
- Open a Windows Explorer window (the keyboard shortcut is Windows logo key+E).
- In the address bar, type %APPDATA%\JamKazam. Press Enter.
- You should now be in the C:\Users\<User>\AppData\Roaming\JamKazam, and can delete Client.ini.
Warning! The application needs to be closed when you manually delete Client.ini. JamKazam saves Client.ini with it's current configuration as it shuts down, so you need to make sure it's not running when you manually delete Client.ini.