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

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

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.

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.
   
   

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.

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.

(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.

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.

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.

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.