Last updated: 16-Mar-2014

How To Authorize
How To Authorize - KARMA Motif
How To Authorize - KARMA Kronos
How To Authorize - KARMA M50
How To Authorize - KARMA M3
How To Authorize - KARMA Oasys
How To Authorize - KARMA MW
How To Authorize - KARMA Triton

To authorize your software: Online Software Registration Form

How To Get A New Full Installer (Registered Owners Only)
• Request Full Installer Form

Sales

• Can I sell my copy of KARMA Software and transfer the license to someone else?


General

• KARMA MW: Korg Karma Music Workstation not located on global ports.

• KARMA Triton: Korg Triton not located on global ports.
• Since I loaded the included .PCG file, when I'm not using the software, my keyboard doesn't make any sound!

Mac

• How do I reset the KARMA software to its default state? Or how do I delete the KARMA Software Preference/Setting files?
• KARMA MW/Triton Crashes with an Error of Type 1 (or other Error) when trying to launch, even after authorization.
• KARMA MW/Triton Crashes with an Error of "-2804 - Error while setting up authorization" when trying to authorize.
• KARMA MW/Triton will not launch. It displays the error dialog "The software could not be opened because "iCAp;InternetConfigLib" could not be found."
• Cannot authorize software, response code is entered, but does not appear to work. Error message such as "Invalid Response to this Challenge" is displayed.

Windows - Installation & Authorization

• After installation, trying to launch the software results in a message "Initialization Error: Code -7."
• After installation, trying to launch the software results in a message "User privileges insufficient to start a low level driver."
• After installation the software cannot be launched and seems to do nothing.
• After installation the software cannot be launched and crashes immediately with an exception, or presents a dialog "KARMA (software name) has stopped working".
• The "InstallShield Wizard" opens to prepare to install, but, after a few seconds an error dialog opens "1607 : Unable to install InstallShield Scripting runtime".
• The KARMA Virtual MIDI Device (VMD) could not be fully installed, -or-
the VMD is marked (inactive) in the KARMA Welcome/About screen.
• You receive an error about "10 MIDI Devices Max" during installation.
IMPORTANT NOTE: All KARMA MW Windows Users (MW version 1.0) should perform an update of the Fonts Registry to correct some font-related problems (click here).
• Initialization Error: Unsupported Driver Call. Check Driver Version.
• Initialization Error: Updated driver required. The driver version is incompatible with this product and requires updating.
• The software freezes on first launch, or crashes with an exception, and you are using a non-English language version of Windows (Unicode issues).
• Initialization Error: This software requires installation of certain device drivers and a reboot before running. Please reboot or reinstall the software.
• There is no “box” in the authorization dialog for me to paste the “Response” into!
• I get a BSOD (Blue Screen Of Death) crash when attempting to launch KARMA MW/KARMA Triton.
• Cannot authorize software, response code is entered, but does not appear to work. Error message such as "Invalid Response to this Challenge" is displayed.
• The RESPONSE code you receive doesn't seem to work, even after making sure that any line breaks or carriage returns are removed.
• After installation, the software crashes the computer when attempting to launch.
• I am getting the error message: "This software requires installation of device driver Tpkd and a reboot before running. Please reboot or reinstall the software."

Windows - Using KARMA Software
• Windows 7: KARMA Oasys hangs on the "Now checking the User Program Bank Types" dialog or does not advance.
• Windows 7: KARMA Software hangs, does not advance, or reports incorrect sysex lengths when trying to receive SysEx dumps of Programs, Combis, or GEs.
• Windows XP: The software crashes at launch with an error of "Unhandled Exception: c00000005 at address: 005b2b46" - or at address: 005b99b6 (or something similar).
• How do I reset the KARMA software to its default state? Or how do I delete the KARMA Software Preference/Setting files?
• KARMA software crashes when attempting to use with Ableton Live 7.
• When I launch, I get an "Unknown Preferences File Error -199 - KARMA will now quit" message.
• Are there any products that KARMA MW/KARMA Triton is not compatible with?
• I am getting frequent crashes with an “Unhandled Exception c00000006.”
• In online Help File, some pictures overlap up the words.
• I cannot grab the top of certain windows because they are off screen.
• KARMA MW/KARMA Triton cannot locate the Karma Music Workstation on the global ports, and I am using an EDIROL UM-1s MIDI Interface.
• How can I temporarily remove KARMA's Virtual MIDI Driver (VMD), i.e. for conflict testing?



General
Issue 091402-01:
KARMA MW: I get the “Korg Karma Music Workstation not located on global ports” message. KARMA MW can’t seem to locate my Korg Karma, even though I have it plugged into the MIDI Interface.

Solution (1):
Ensure you have the latest version of KARMA MW. Note: If you installed KARMA MW from a CD, there is a chance that you are running an out-of-date version of the software.

Solution (2):
KARMA MW communicates with the keyboard through SysEx (System Exclusive) data. Check that you definitely enabled SysEx communications by checking-marking the “Exclusive” checkbox on page (2.1) of the keyboard’s Global mode. Also make sure that your MIDI Interface is not somehow filtering SysEx data out of the MIDI stream.

Solution (3):
You Korg Karma must be running OS 2.0. If you are not yet upgraded to 2.0, [click here].

Solution (4):
If you are running Windows and using an EDIROL UM-1s MIDI Interface, make sure that you have installed the latest version of the Drivers (1.5.1 or later). [click here] for more information.



Issue 031604-01:
KARMA Triton: I get the “Korg Triton not located on global ports” message. KARMA Triton can’t seem to locate my Korg Triton, even though I have it plugged into the MIDI Interface.

Solution (1):
KARMA Triton communicates with the keyboard through SysEx (System Exclusive) data. Check that you definitely enabled SysEx communications by checking-marking the “Exclusive” checkbox on page (2.1) of the keyboard’s Global mode. Also make sure that your MIDI Interface is not somehow filtering SysEx data out of the MIDI stream.


Solution (2):
If you are running Windows and using an EDIROL UM-1s MIDI Interface, make sure that you have installed the latest version of the Drivers (1.5.1 or later). [click here] for more information.


Issue 072605-01:
Since I loaded the included .PCG file, when I'm not using the software, my keyboard doesn't make any sound!

The .PCG file that you loaded also contains Global Settings. One of the settings is to turn Local Control On to "Off", in the Global MIDI Page. Return this setting to "On", and the keyboard will again be connected to the internal tone generator. Note that for proper operation with the KARMA software, this setting should be returned to "OFF", or you will get "doubled" notes when operating the software. For older software, such as KARMA MW or KARMA Triton, you may need to do this manually each time you use the program. For newer software such as KARMA Kronos, KARMA Motif, KARMA Oasys, KARMA M3 and KARMA M50, the software attempts to automatically control this setting - although (for example), if you disconnected or turned off the keyboard before quitting the application, the setting may remain in the "OFF" position, thereby silencing the keyboard the next time you try to use it.


Issue 112808-01:
How do I reset the KARMA software to its default state? Or how do I delete the KARMA Software Preference/Setting files?

Deleting the Preferences files is sometimes a good way to fix crashing problems that may have come up. To do so, quit/exit the KARMA Software if it is open. Delete the following files, and relaunch the software. You will then be back to the default startup state, and will need to reset various settings to get them back the way you had them.

Mac OS X:

(The end part of the name shown as (xx) below corresponds to the version of software, such as KARMA Oasys, KARMA M3 etc. Also note that ~ indicates your User folder, not the Library folder on the root of the hard drive. You want the Library folder inside your user account folder.)

~/Library/Preferences/com.karma-lab.KARMA(xx).plist
~/Library/Preferences/KARMA Preferences/KARMA (xx) Prefs

Windows XP:

(The files are in the place where you installed them, which by default is the Program Files folder. Note that the exact folder name depends on which software you have installed, so the (xx) below represents KARMA Oasys, or KARMA M3 etc.)

Older versions of the software:

C:/Program Files/Karma Lab/KARMA (xx)/KARMA.INI
C:/Program Files/Karma Lab/KARMA (xx)/KARMA Resources/KARMA (xx) Prefs.kpf

Newer versions of the software - there is no "Karma Lab" folder:
• KARMA Motif - all version
• KARMA MW and KARMA Triton - version 1.3.2 and higher
• KARMA Kronos, KARMA Oasys, KARMA M3 and KARMA M50 - version 2.2.9 and higher

C:/Program Files/KARMA (xx)/KARMA.INI
C:/Program Files/KARMA (xx)/KARMA Resources/KARMA (xx) Prefs.kpf

Windows Vista/Windows 7/Windows 8:

(The files are in the place where you installed them, which by default is your User Account Documents folder - the exact name depends on your user account. Note that the exact folder name depends on which software you have installed, so the (xx) below represents KARMA Oasys, or KARMA M3 etc.)

Older versions of the software:

C:/Users/MyUserAccount/Documents/Karma Lab/KARMA (xx)/KARMA.INI
C:/Users/MyUserAccount/Documents/Karma Lab/KARMA (xx)/KARMA Resources/KARMA (xx) Prefs.kpf

Newer versions of the software - there is no "Karma Lab" folder:
• KARMA Motif - all version
• KARMA MW and KARMA Triton - version 1.3.2 and higher
• KARMA Kronos, KARMA Oasys, KARMA M3 and KARMA M50 - version 2.2.9 and higher

C:/Users/MyUserAccount/Documents/KARMA (xx)/KARMA.INI
C:/Users/MyUserAccount/Documents/KARMA (xx)/KARMA Resources/KARMA (xx) Prefs.kpf








Mac
Issue 091502-01:
KARMA MW/Triton Crashes with an Error of Type 1 when trying to launch, even after authorization.

1) There is a known conflict with Action Utilities Action Menus. Please disable this extension when using KARMA MW/Triton. You can also leave Action Menus running, but tell it to ignore KARMA MW/Triton in the control panel settings for Action Utilities.

2) KARMA Software (under OS 9 or Classic OS 9) requires the following system extensions to be present and enabled on your system to run:
- CarbonLib
- Open Transport
- Internet Config Extension
- URL Access
- QuickTime

If KARMA Software crashes the first time you try to run it, or you see a warning dialog with a message “Required software extensions are missing. Click on the “OK” button and you will be transferred to the PACE website, where an installer can be downloaded,” one or more of these extensions is likely disabled or missing. You don’t need to go to the PACE website.

Note that the libraries associated with Open Transport and QuickTime are spread across several extensions. It is recommended that you enable all other related extensions that have OT, Open Transport, or QuickTime in the name.


Issue 011205-01:
KARMA MW/Triton Crashes with an Error of "-2804 - Error while setting up authorization" when trying to authorize.
Issue 062705-01
KARMA MW/Triton will not launch. It displays the error dialog "The software could not be opened because "iCAp;InternetConfigLib" could not be found."

KARMA Software (under OS 9 or Classic OS 9) requires the following system extensions to be present and enabled on your system to run:
- CarbonLib
- Open Transport
- Internet Config Extension
- URL Access
- QuickTime

Note that the libraries associated with Open Transport and QuickTime are spread across several extensions. It is recommended that you enable all other related extensions that have OT, Open Transport, or QuickTime in the name.


Issue 062805-01:
Cannot authorize software, response code is entered, but does not appear to work. Error message such as "Invalid Response to this Challenge" is displayed.

Description:
Sometimes, when the RESPONSE code is sent through e-mail, line breaks (carriage returns) get inserted into the text. When you copy and paste it into the RESPONSE Box, the line breaks cause the code to become invalid.

Solution:
Make sure all line breaks and carriage returns are removed from the code (see diagrams below). You may need to place the cursor in the RESPONSE Box to the left of each word, remove the "space" (which may actually be a line break), and replace the space. Also, you can manually enter the words, in all capital letters with a space between each one, if all else fails.

Note: Mac dialogs shown, but problem and solution is the same on Windows.





Windows - Installation & Authorization
Issue 070913-01
After installation, trying to launch the software results in a message "Initialization Error: Code -7."
This is an issue that can occur on Windows Vista and Windows 7 when any of the following known products are in use:

  • Comodo firewall
  • Makrolock Antivirus
  • Panda Security
  • Norton Online Backup
  • F-Secure Internet Security (unconfirmed)
  • Sentinel HASP License Manager (older versions?)
  • "Browser Manager" (mngr.exe)
  • "Babylon Toolbar" (browserprotect.exe)
  • Anything from the company PerformerSoft LLC
  • browsermngr.exe AND brwmngr.exe (part of something called "Browser Manager")
  • Sidekick Manager (sidemngr.exe; PerformerSoft LLC product)
  • InstallBrain Installer (ibsvc.exe; PerformerSoft LLC product)
  • BullGuard Anti-Virus
This is caused by a conflict between the PACE drivers required to operate the KARMA Software, and the system filter drivers and the user mode components used by these applications above modifying the result returned by some Windows API functions in a way that is not 100% compatible with what is specified by Microsoft. The solution at this time is to uninstall the above products in their entirety and reboot the system.


Issue 042312-01
After installation, trying to launch the software results in a message "User privileges insufficient to start a low level driver."
1. The KARMA Installer installs drivers for PACE Interlok (copy protection). Depending on the time frame, there may be a newer version of the drivers required to fix conflicts. Therefore, simply try downloading and installing the latest PACE drivers from their website, in the upper right corner - after you have installed KARMA. Then reboot and try launching again. Download drivers here:

www.paceap.com  PACE Drivers (Interlok)

2. (Windows 7 and Vista) - Locate the KARMA exe, right-click for properties, and try turning on "Run as Administrator."


Issue 122611-01, Issue 031912-01
After installation the software cannot be launched and crashes immediately with an exception, or presents a dialog "KARMA (software name) has stopped working".  OR

After installation the software cannot be launched and seems to do nothing.
1. Windows DEP (Data Execution Prevention) may be blocking the app from launching.

- Open System by clicking the Start button , right-clicking Computer, and then clicking Properties.
- Click Advanced system settings. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
- Under Performance, click Settings.
- Click the Data Execution Prevention tab. It's likely you have it set to the second option, "Turn on DEP for all programs and services except ones I select".
- Option 1: set it as shown in FIG. A (turn on DEP for essential Windows programs and services only), and then you will be told to reboot your computer.
- Option 2: set it as shown in FIG. B (Turn on DEP for all programs and services except ones I select), and then add the KARMA XXXXX.exe program to the list, using the Add button. The diagram below shows KARMA Motif, but it would be the same for any of the KARMA software programs. The exact location of the program will be different depending what your OS is, and also which program it is, so the easiest way to find out where the program is located is to use the desktop shortcut > Properties to reveal the location of the original file. You might need to restart your computer for the changes to take effect.

Windows DEP

2. If you have an ILok device connected, please remove it and try launching the software again.

3. The KARMA Installer installs drivers for PACE Interlok (copy protection). Depending on the time frame, there may be a newer version of the drivers required to fix conflicts. Therefore, simply try downloading and installing the latest PACE drivers from their website, in the upper right corner - after you have installed KARMA. Then reboot and try launching again. It absolutely cannot hurt, and it may solve your problem!

www.paceap.com  PACE Drivers (Interlok)


Issue 071011-01
The "InstallShield Wizard" opens to prepare to install, but, after a few seconds an error dialog opens "1607 : Unable to install InstallShield Scripting runtime".
Rename the InstallShield folder:
  1. In Windows Explorer or in My Computer, open the folder: C:/Program Files/Common Files/
  2. Right-click the InstallShield folder, and then click Rename.
  3. Type InstallShield1, and then press ENTER.
  4. Retry the installation.

If this does not solve the issue, more help on this can be obtained at http://support.microsoft.com/kb/910816 or http://support.microsoft.com/kb/888019



Issue 012804-01
The KARMA Virtual MIDI Device (VMD) could not be fully installed, -or-
the VMD is marked (inactive) in the KARMA Welcome/About screen, -or-
you receive an error about "10 MIDI Devices Max" during installation.

Background

  1. The "Windows Registry" is a big, hidden database the Windows Operating System uses to keep track of everything that has been installed on your computer. This includes application software and hardware/software device drivers.

  2. The audio and midi sections of the Windows Registry are slightly "weird" in that a new entry is created:
    - every time you install a new device (expected)
    - every time you reinstall a driver (unexpected)
    - every time you MOVE a hardware device from one port to another (unexpected). An example of the latter would be if you moved a USB midi interface from one physical USB port to another.

  3. When a midi device is installed, a "midi" registry entry is created. The first entry is called "midi"; the second entry is "midi1"; the third "midi2", etc.

  4. Also, some device manufacturers "uninstall" programs forget to remove midi registry entries.

Problem

All of the above would NOT be a problem except that Windows NT/2000/XP only "recognizes" up to 10 midi devices (midi through midi9). Due to "unnecessary" midi registry entries, the KARMA software installer may have registered the KARMA Virtual MIDI Driver (karmadrv.dll) into slot "midi10" (or higher). In this case, Windows won't actually see the driver.

Solution Part A - Diagnose the Problem

  1. WARNING: This solution requires that you manually edit your registry which, unfortunately, can be a risky thing to do (i.e., if you're not extremely careful and don't follow the instructions exactly, you could seriously damage your system). Therefore, if you are running XP, you should play it safe by first creating a Windows Restore Point so that you can restore your previous state if something goes wrong. If you are not familiar with the System Restore process, click the "Start" button, then choose "Help and Support" and search for "restore point".

  2. Open the Windows Registry editor by clicking the Start menu, selecting Run, then typing "regedit" and clicking OK.

  3. Along the left-hand side of the regedit window, navigate to the following folder:
    My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Drivers32

  4. In this folder /Drivers32, you are looking for the entries that start with "midi", "midi1", etc. If you see any entry with a number of "midi10" or higher, this means that Windows will not USE that information (and therefore not use that device).

  5. Associated with each "midi" entry is a filename. For example, the "midi" entry is often associated with "wdmaud.drv". At this point, you should be able to find the entry for the KARMA Virtual MIDI Device (karmadrv.dll). It is likely to been in entry "midi10" or higher.

  6. There is a second registry "description folder" that you can use to get a description of these midi entries. Navigate to the following folder:
    /HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Drivers.desc

    In this folder, you should see an entry for "karmadrv.dll" with a description of "KARMA Virtual MIDI Device."

  7. Using these two folders, look for "duplicates" (like Midi1 and midi2 referring to the same file) or "old entries" (e.g., entries that refer to a device that you may have uninstalled long ago).

The image below shows the KARMA VMD driver (karmadrv.dll) in entry "midi10". It also shows how some drivers (e.g., usbmn2x2.dll, midixyz.dll) have been duplicated.


Karma VMD Driver (karmadrv.dll) shown in "midi10" entry.
Unfortunately, Windows ignores drivers above "midi9".

Solution Part B - Fix the Problem

  1. You will "fix" the problem by deleting at least one of the first 10 ("midi" thru "midi9") registry entries so that "there is room" for the Karma midi driver. (Note: Since you're already here, you may want to clear out all duplicates/unused entries... but it's only necessary that you open 1 entry in order to install the VMD).

  2. First, if you come across drivers that you are no longer using, you should uninstall them via the Windows Control Panel. However, if you have uninstalled the driver and still see entries here in the registry, you'll want to remove the entry manually. For example, let's say that "midi4" referred to a driver that you have uninstalled and you are sure you are no longer using. To remove the "midi4" entry, you would simply right-click on "midi4" and choose "Delete". (Again: Please be careful when removing registry entries! You may want to print the entries or export the folder so that you can restore the changes if something goes wrong).

  3. Next, remove multiple entries of the same driver. For example, if you see "usbmn2x2.dll" in entry "midi1", "midi2", and "midi3", you should be able to remove the entries in "midi2" and "midi3" without any consequences.

  4. Finally, we're going to "move" the KARMA VMD entry into the first free slot that you created. Let's say the first free entry is now "midi2" and the KARMA VMD driver (karmadrv.dll) is in "midi10". To move it, right-click on "mid10", choose "Rename", and rename it to "midi2". That's all there is to it.

  5. If you feel like doing a "full" cleanup at this point, feel free to rename your other midi entries so that there are no empty slots and they are all sequential. That way, you'll minimize problem if/when you install future MIDI hardware/software.



Issue 021808-01
The software freezes on first launch, or crashes with an exception, and you are using a non-English language version of Windows (Unicode issues).
(Windows 7/Vista) - Try changing the settings for non-Unicode program support:

1. Go to your Control Panel.
2. Click on "Clock, Language and Region."
3. Click on "Region and Language."
4. On the Administrative tab, set "Language for non-Unicode programs" to "English (United States)," by clicking the "Change system locale..." button. (Note that on Vista, the applicable section is at the top of the Administrative tab.)
5. Reboot and try launching the software again.



(Windows XP) - Try changing the settings for non-Unicode program support:

1. Go to your Control Panels.
2. Open "Regional and Language Options."
3. On the Advanced tab, set "Language for non-Unicode programs" to "English (United States)."
4. Reboot and try launching the software again.



Issue 102402-01
IMPORTANT NOTE: All KARMA MW Windows Users (MW version 1.0) should perform an update of the Fonts Registry to correct some font-related problems.

There was a slight problem with the KARMA MW 1.0 Installer program where it did not correctly update the Registry for the Fonts that are installed as part of the installation. Symptoms of the problem include Help File pictures overlapping the text, and display of all labels in the editing windows in an incorrect font. All Windows users should perform an update of the Registry by performing the following:

1. Quit KARMA MW if it is running.
2. Open and close the Fonts folder, which can be done by going to the Start Menu > Control Panels > Fonts.
3. Reboot the computer and relaunch KARMA MW. It should now be using the correct fonts.

For the technically inclined, in the Registry Editor, the location of the keys should be:

Windows 98, 98SE, ME:
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Fonts/

Windows 2000, NT, XP:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/Current Version/Fonts/

...where you should find:
..........Name............................Data
KARMAbm1 (96 dpi)..........KARMABM1.FON
KARMAbm2 (96 dpi)..........KARMABM2.FON
KARMAbm3 (96 dpi)..........KARMABM3.FON
KARMAbm4 (96 dpi)..........KARMABM4.FON


Issue 091402-02:
When I try to launch KARMA MW/Triton for the first time on my Windows machine, I get this error: “Initialization Error - Unsupported Driver Call. Check Driver Version” or “Updated driver required. The driver version is incompatible with this product and requires updating.”

KARMA MW/Triton is protected with a system known as PACE Interlok. Normally, the installer installs a PACE driver on your system, but not if one is already there. It is likely that there is an older version of the PACE Interlok driver installed on your system by some other software. You must manually replace it with the newest version, which can be downloaded from PACE’s website at:

http://www.paceap.com/dldrvr.html

Simply download the installer, run it, and then *reboot* your machine. Now you should be able to run the KARMA software for the first time and get to the authorization section of the procedure.

To check the version of the driver (for those technically inclined), navigate to the folder where the OS is installed. For example, in Windows 98, this is generally "C:/Windows". In that folder is another folder called "System" where the driver is installed. It is called "Tpkd.vxd".

If you right click that file and select "Properties" from the popup menu and in the screen that appears select the tab named "Version". You should now see the file version.

The same goes for XP and NT but the driver has a different name and location as shown below.

The version should be greater than or equal to 5.3.2.2374, which is current for KARMA MW/Triton 1.3.0.22 as of Dec 2004. You can run an Interlok protected executable with a later version driver, but not an earlier one.

Windows 98SE/ME
============
File : C:/Windows/System/Tpkd.vxd

Windows XP
============
File : C:/WINDOWS/system32/drivers/TPkd.sys
- or -
File : C:/WINNT/system32/drivers/TPkd.sys

Windows 2000/NT
============
File : C:/WINNT/system32/drivers/TPkd.sys


A list of some FAQs related to PACE can be viewed at:

http://www.paceap.com/faquser.html


Issue 100402-01:
When I try to run KARMA MW or KARMA Triton for the first time, I get “Initialization Error: This software requires installation of certain device drivers and a reboot before running. Please reboot or reinstall the software.”

KARMA MW/Triton is protected with a system known as PACE Interlok. It appears that the InterLok components are not being installed at all, or not in their respective locations.

If KARMA MW/Triton is currently installed:

1a) Uninstall it, using the Add/Remove Programs function in your System Settings.

2a) Open your C:/Program Files/ folder, and if a Karma Lab or KARMA MW folder is still there, delete it.

3a) Reinstall the software.

4a) Verify that the error persists.

If the error persists we will need to do the following. Please be aware that the following involves dealing with the System Registry. If the wrong key is deleted or changed, it can render a system useless. It is very important to follow the instructions below precisely.

1b) Select “Run” from the “Start” button and then type “regedit”. This will open the Registry Editor. It is very important at this point that nothing else is touched within the registry other then the keys we are about to show you.

2b) Make sure “My Computer” from the registry editor is highlighted, click “Edit” from the menu and select “Find...”. Make sure all the checkboxes are checkmarked.

3b) Type in 'tpkd' (without quotes) to search for it.

4b) When a tpkd entry is found, delete it and repeat this process until no more tpkd entries can be found. If you find an entry that can not be deleted, this is OK - just continue on to the next one.

Now that your registry has been purged of all tpkd driver entries, you will need to reinstall them again via the PACE driver installer kit.

5b) Reboot the system.

6b) Download the PACE driver kit from http://www.paceap.com/dldrvr.html.

7b) Run the PACE installer.

8b) Reboot the system once the install has completed.

9b) Once rebooted, run KARMA MW or KARMA Triton and see if you can now make it to the authorization dialog.

To verify that the “tpkd.sys” driver has installed and loaded properly (on NT and XP systems, not 9x/ME), one can:

1c) Open up a command prompt by choosing “Run” from the “Start” menu and entering the word “command.”

2c) Type the following syntax (minus the quotation marks) at the C:/> prompt: “net start tpkd”

3c) The following text should appear, “The requested service has already been started.” If so, the driver has been properly installed and loaded.

If after following the above procedure there is no improvement, please let us know.



Issue 100402-02:
There is no “box” in the authorization dialog for me to paste the “Response” into!

As shown in the following diagram, on some systems the font size can be changed in a way that causes the text to be too large for the dialog, and actually moves the Response Box off the screen:
This is caused by the Font Size setting in the System Settings being set to a Custom (larger) font size. To fix this, right-click on the desktop and select “Properties”. Click on the “Settings” tab, click the “Advanced” button, and change the Font Size to “Small (96 dpi)”. Click on “OK” for everything, and then reboot your computer. The next time you run KARMA MW you should be back to the normal screen where you can paste your Response in the Response Box.



Issue 102702-01:
I get a BSOD (Blue Screen Of Death) crash when attempting to launch KARMA MW/KARMA Triton.
First of all, make sure you have updated to the latest version of KARMA MW/KARMA Triton. Version 1.3.1.24 fixed an issue with getting a BSOD when attempting to launch the software.

Secondly, see the next issue below:

Issue 102702-02:
Are there any products that KARMA MW/Triton is not compatible with?

There are a few drivers and other software products that are incompatible with the PACE copy protection system. This can cause the “Blue Screen Of Death” or other crashes when attempting to launch the KARMA software. They are:

Cybermedia Products
Cybermedia 95, 98, 2000 - these products are incompatible with PACE and cannot be run at the same time. There is no other resolution other than to remove them from the computer running the KARMA software.

McAfee VirusScan
Problems with McAfee VirusScan can be resolved by using the latest InterLok driver 3.0.7.840 or higher. See Issue 091402-02 for a description of how to check the driver version, and get the latest PACE Drivers.

Chernobyl Virus
The W_95.CIH virus is an issue that we have not seen for longer than two years now. This can be resolved by downloading an MS-DOS based virus scanner which will eliminate the virus. The program can be found here: http://www.symantec.com/avcenter/kill_cih.html.

Sophos Anti-Virus
Sophos would cause system to reboot at the moment of authorization (i.e. the challenge response window). This can be resolved by using the latest InterLok driver 3.0.7.840 or higher. See Issue 091402-02 for a description of how to check the driver version, and get the latest PACE Drivers.

ASPack Software ASProtect.
If software protected by PACE and ASProtect are running concurrently, a reboot may be experienced. There is no known workaround to this issue other than to not run software protected by PACE and ASProtect software together.



Issue 062805-02
The RESPONSE code you receive doesn't seem to work, even after making sure that any line breaks or carriage returns are removed.

Description:
Check the CHALLENGE code that you originally sent against the CHALLENGE code currently displayed in the authorization dialog.

In a few cases, a computer has a situation where every time the authorization dialog is launched, the challenge code is different. So of course, by the time you receive the response code, it doesn't work because you open the dialog and the challenge has changed.

Solution:
Launch the authorization dialog, send the CHALLENGE code, and then DO NOT CLOSE the dialog. Leave it open until you receive the RESPONSE code back from us. Then you will be able to enter it and everything will be fine after that.

Updated 12-Mar-2006: This issue should be resolved starting with version 1.3.1.24 of KT or MW. Please update to this version by downloading an updater from the Updates Page, or contact support for a full installer.


Issue 090405-01
After installation, the software crashes the computer when attempting to launch.

Occasionally, a user will have some other software on the computer that also uses PACE, and an older version of the PACE Interlok Driver is already installed. This prevents the newer driver used by KARMA Software from being installed, which can cause problems and crashes (in this example, both programs can use the newer driver, but KARMA Software cannot use the older driver.)

Solution:
Manually install the latest PACE drivers and reboot. They can be downloaded from:
http://www.paceap.com/dldrvr.html


Issue 070809-01
I am getting the error message: "This software requires installation of device driver Tpkd and a reboot before running. Please reboot or reinstall the software."

This means that either the PACE Interlok Driver is missing, has become corrupted, is too old (perhaps having been replaced by installing other PACE-protected software), or has been moved or otherwise cannot be located.

Solution:
Manually install the latest PACE drivers and reboot. They can be downloaded from:
http://www.paceap.com/dldrvr.html





Windows - Using KARMA Software
Issue 071113-01
Windows 7: KARMA Oasys hangs on the "Now checking the User Program Bank Types" dialog or does not advance.

-- OR --
Windows 7: KARMA Software hangs, does not advance, or reports incorrect sysex lengths when trying to receive SysEx dumps of Programs, Combis, or GEs.

Windows 7 itself appears to have an issue where it cannot receive bulk SysEx dumps properly if it is being sent MIDI clock at the same time. We have tested this issue with three different MIDI Interfaces from three different companies, and they all have the same problem.

This does not happen with the Korg USB Driver, which is what you should be using if you have an M50, M3 or Kronos. So generally, this problem will only manifest itself with an OASYS, original Karma Workstation or Triton using a regular MIDI Interface.

The solution is to set the keyboard's MIDI Clock Mode to "External" (or "Auto" if that option exists) on the Global > MIDI tab, and have the software send the keyboard MIDI Clock Sync, which is the recommended setting anyway. More details can be found in the software's Help File at the end, in the Appendices chapters relating to "Communication Configuration."


Issue 091602-01:
When viewing the online Help File, some of the pictures overlap lines of text and they cannot be read.

There was a slight problem with the KARMA MW 1.0 Installer program where it did not correctly update the Registry for the Fonts that are installed as part of the installation. See Issue 102402-01.



Issue 102402-02:
I cannot grab the top of certain windows because they are off screen.


There should be a vertical scroll bar on the right side of your screen, which controls the position of the editor windows within the overall application window. You can scroll them into view.

If this does not work for some reason, you can always reset the windows to their default “factory” locations by doing the following:

1. Exit the KARMA MW/Triton application if it is running.

2. Throw away the KARMA MW/Triton Preferences (.kpf) file since it stores the positions of all editor windows the last time you quit the application. Assuming you have a standard installation, the name and location of this file is:

MW: C:/Program Files/KARMA Lab/KARMA MW/Resources/KARMA MW 1.x Prefs.kpf
Triton: C:/Program Files/Karma Lab/KARMA Triton/Resources/KARMA Triton 1.x Prefs.kpf

3. Throw away the INI file (which stores the size and position of the overall application window.) Assuming you have a standard installation, the name and location of this file is:

MW: C:/Program Files/KARMA Lab/KARMA MW/KARMA.INI
Triton: C:/Program Files/KARMA Lab/KARMA Triton/KARMA.INI

4. Relaunch KARMA MW/Triton.

Note that the Preferences file also stores settings like the Global MIDI In/Out Ports etc. Therefore, the KARMA software may not initially detect your keyboard and you may have to rerun the MIDI Setup Assistant in order to reconfigure the Global MIDI Ports.



Issue 092602-01:
I am getting frequent crashes with an “Unhandled Exception c00000006.”

Some users have reported that this can be caused by having many applications open in the background, such as virus checkers, AIM, etc. Try quitting all other open applications and see if the problem goes away. You can use the task manager to exit open background applications. If you discover a definite conflict, please report it to support@karma-lab.com.



Issue 102002-01:
KARMA MW/KARMA Triton cannot locate the Karma Music Workstation/Triton on the global ports, and I am using an EDIROL UM-1s MIDI Interface.

Make sure that you have installed the latest version of the EDIROL UM-1 USB Driver (1.5.1 or later). There was a definite problem with version 1.4, which was included on the Edirol CD that we tested.

The latest drivers can be found on Roland’s site at Downloads.

You can determine which version of the driver you have loaded by doing the following:

1. Open the Control Panel, and double-click “System.”
2. Click the “Hardware” tab, and then click the “Device Manager” button.
3. Double-click “Sound, video and game controllers.”
4. Double-click “EDIROL UM-1 USB Driver.”
5. Click the “Properties” tab, and in the Multimedia Devices field, double-click “MIDI Devices and Instruments.”
6. Select “EDIROL UM-1 USB Driver,” and click the “Properties” button.
7. Click the “Settings” button to access the “EDIROL UM-1 USB Driver Settings” dialog box. Here you can view the version number.


Issue 041704-01:
When I launch, I get an "Unknown Preferences File Error -199 - KARMA will now quit" message.

Delete the Preference File(s) and run it again. In a default installation, they are located at:

KARMA MW 1.0
C:/Program Files/KARMA MW 1.0/KARMA.INI
C:/Program Files/KARMA MW 1.0/Resources/KARMA MW 1.0 Prefs.kpf

KARMA MW 1.1 and later
C:/Program Files/Karma Lab/KARMA MW/KARMA.INI
C:/Program Files/Karma Lab/KARMA MW/Resources/KARMA MW 1.1 Prefs.kpf

KARMA Triton
C:/Program Files/Karma Lab/KARMA Triton/KARMA.INI
C:/Program Files/Karma Lab/KARMA Triton/Resources/KARMA Triton 1.1 Prefs.kpf

Note: this means a new Preferences File will be created, and you may need to reset some of your previous settings, such as the MIDI In & Out setup and other settings that are located in the Preferences Editor (Edit Menu > Preferences).


Issue 090505-01:
How can I temporarily remove KARMA's Virtual MIDI Driver (VMD) (i.e. for conflict testing)?

To do so, you need to go into the Registry.

Select “Run” from the “Start” button and then type “regedit”. This will open the Registry Editor. It is very important at this point that nothing else is touched within the registry other then the key we are about to show you.

In a typical installation (XP), the driver entry will be located under:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Drivers32

It's the one where the Data field says "karmadrv.dll" (should be "midi1" or "midi2", etc.). Select this entry and DELETE it.

(If you have difficulty locating the entry, you can search for it: make sure “My Computer” from the registry editor is highlighted, click “Edit” from the menu and select “Find...”. Enter "karmadrv.dll" and make sure all the checkboxes are checkmarked.)

After deleting the entry, you then need to reboot. The DLL will still be there, but XP won't know to load it. When running KT or MW, you will see "VMD not active" or something similar in the start up screen.

To reinstall the driver at a later time, go to the same place in the Registry, create a new entry, enter "karmadrv.dll" in the data field, and reboot. The next time you run KT/MW, you should see the driver version number in the start up screen.



Issue 022008-01:
• KARMA software crashes when attempting to use with Ableton Live 7.

There appears to be a conflict between the Edirol FA-66 interface and settings in Ableton Live 7. In Ableton Live 7 go to preferences, then audio. Under audio device, change the driver type from ASIO to MME/DirectX. Then select your soundcard's DX setting for the audio input and output device.



Issue 100208-01:
(Windows XP) The software crashes at launch with an error of "Unhandled Exception: c00000005 at address: 005b2b46" - or at address: 005b99b6 (or something similar).


There may be a conflict with the Yamaha Studio Manager USB Driver. According to one report, the Yamaha USB Driver v 2.1.4 was causing this issue. Downloading the latest version of the Yamaha USB driver (Version 2.2.3 for XP/2000 at the time this article was updated) and reinstalling it fixed the issue.

If this does not solve the issue, try completely removing the Yamaha USB Driver. It has been reported that even if you use the Windows Add/Remove Programs Utility to remove the Yamaha Studio Manager, it might not actually remove the USB Driver. You should follow the steps below to check and fix the problem:

Solution Part A - Identify and remove the Yamaha USB Driver:
  1. Go to the C:Windowssystem32 directory. Locate the xgusb.cpl driver. If you cannot find it, then it is not installed or has been successfully uninstalled.
  2. If you locate it, right-click on the file and check the version, under the Version tab. Go to http://www.yamahasynth.com/download/ and make sure you have the latest version, or download the latest version. If not, download it.
  3. If doing an install of a newer version, remove this version to the trash (or a temporary folder).
  4. Proceed to the next section and fix the Registry. After completing that step, restart the computer before installing any new drivers.
Solution Part B - Fix the Registry
  1. WARNING: This solution requires that you manually edit your registry which, unfortunately, can be a risky thing to do (i.e., if you're not extremely careful and don't follow the instructions exactly, you could damage your system). Therefore, you should play it safe by first creating a Windows Restore Point so that you can restore your previous state if something goes wrong. If you are not familiar with the System Restore process, click the "Start" button, then choose "Help and Support" and search for "restore point".

  2. Open the Windows Registry editor by clicking the Start menu, selecting Run, then typing "regedit" and clicking OK.

  3. Along the left-hand side of the regedit window, navigate to the following folder:
    My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Drivers32

  4. In this folder /Drivers32, you are looking for the entries that start with "midi", "midi1", etc. (For one thing, if you see any entry with a number of "midi10" or higher, this means that Windows will not use that information (and therefore not use that device). For more on fixing the "10 MIDI Drivers" issue, see this issue.)

  5. Associated with each "midi" entry is a filename. For example, the "midi" entry is often associated with "wdmaud.drv". At this point, you should look for an entry associated with "xgusb.cpl", as shown below, with the Yamaha USB Driver (xgusb.cpl) in entry "midi3":



  6. Delete the xgusb.cpl entry (right-click: Delete), close the registry, and reboot your computer. If you just want to test whether the KARMA software works at this point, try launching KARMA Software again (without installing any new drivers.) If it starts up with no problem, then you have identified the culprit. You can then install the latest Yamaha Drivers if you wish to and see if it still works after doing so.



Sales
Issue 063007-01:
Can I sell my copy of KARMA Software and transfer the license to someone else?

================================================================
The policy regarding transfer of ownership of KARMA Software (as of Apr 4, 2012) is as follows:
================================================================

1) There is a charge of $39.95 US to transfer ownership of the license. This covers the work involved on our side to change records, provide authorization codes, tech support in the future to the new owner, future updates, etc.

2) Software that was used to qualify for a discount when purchasing a different version of software MAY NOT be transferred. In other words, if you owned a copy of KARMA MW (for example) and use it to qualify for a previous owner discount when ordering KARMA M3 software, you may not transfer the KARMA MW license to someone else.

3) A software license cannot be transferred more than once. If the license was already transferred to you, you cannot transfer it to someone else.

4) The previous owner must send an e-mail to support@karma-lab.com stating that they have sold the software and no longer intend to use it. They must then delete the software from any computers in their posession, and will then no longer be eligible for free updates, upgrades, or authorization codes.

5) Once the license has been transferred, the previous owner cannot use it to qualify for a "Previous Owner Discount" on some other KARMA software.

6) To take advantage of this offer, the new owner needs the customer registration number of the software, which the previous owner should be able to supply you with (note: it is NOT the challenge/response code.) It is a number that looks like "KMW-XXXXX-XXXXX-XXXXX" or "KTR-XXXXX-XXXXX-XXXXX". If this number is not available, we can generally look it up provided the original owner contacts us according to step 4.

7) Once you have the number, the license transfer option can be ordered online at the Karma-Lab Store:

Purchase the License Transfer Option

8) On that page, you enter the Customer Registration Number from step 5, and complete the rest of the order. (If you do not have the customer registration number, we can retrieve it for you from the system provided the previous owner contacts us as mentioned in step 4.)

9) Then, you will receive a download link to the full installer of the latest version, for all supported platforms, and you can choose which installer to download.

Note: this policy is subject to change at any time.