Korg Forums

I am attempting for the first time to use the Kronos Editor with my Kronos, and having no success. Here's what I am working with:

Kronos Editor 2.0.0 (Standalone)
Kronos OS 2.0.6
Kronos MIDI PC Driver 1.14 r8
Windows 7 Pro 64-bit SP1

I am experiencing two different errors when the Kronos and the Editor try to communicate:
1) Within the Kronos Editor, I see "Internal Error - failed to find Custom dll/dylib file"
2) On the Kronos itself, I see something along the lines of "Midi Receiving Error F0 42 30 68 73 01 06 00 7F 04 ... (xxxx BYTES).
(The two errors do not necessarily happen at the same time)

The end results are that no data transfer between the Kronos and the Editor, and the Editor eventually crashes.

If anyone else has worked through a similar issue, I'd appreciate some guidance. Thanks!

soundspossible wrote: 1) Within the Kronos Editor, I see "Internal Error - failed to find Custom dll/dylib file"

I'm far from an editor guru but it seems your Korg driver isn't loading or has not been installed or installed correctly.
If you haven't already, do a search (Here or web) There were many who have had this problem.. I'd start here.

Thanks Lou. I haven't yet stumbled upon a thread with a solution to this problem, but I'll keep trying. I have already tried reinstalling/repairing the driver (even temporarily trying the older r6 driver) to no avail. I've also tried reinstalling the Editor, which didn't work. If it is still installed incorrectly after all of that, I'm at a loss.

There are a few variables I recall, one of which, something about on Windows you can only have a certain amount of drivers loaded in the system and how to go about removing.. something to that effect? Sorry, I'm Mac.

Maybe this will help?

http://www.korgforums.com/forum/phpBB2/ ... hp?t=77648

Thanks again Lou. I am below 10 drivers so that doesn't appear to be the problem. I did have some degree of success switching to the Yamaha driver as described in this thread: http://www.korgforums.com/forum/phpBB2/ ... hp?t=83967

It isn't perfect. The Editor still displays "Internal Error - failed to find Custom dll/dylib file" often, but I'm able to dismiss the message (sometimes I have to click several times in succession) and continue work. If there's a better solution, I'd like to know, but at least I'm unblocked for the moment.

At this point, I've tried every trick I could find here on the forum, including editing the registry, but the error "Internal Error - failed to find Custom dll/dylib file" in the editor persists. Changing the driver to either the base Windows one or Yamaha allows communication with the Kronos, so I guess I just have to accept partial victory and move on. I put in a request to Korg support. If they reply with a solution that works, I will post it here.

This has nothing to do with the Korg drivers. What is happening is the program loads a number resource dlls. Before it attempts to load each dll, as a safety measure it asks the OS to verify that the file is there. In your case, the OS is replying back "the file was not found".

We have seen this happen with one other person. Their solution was to put the program on a different computer and and everything was then fine. I don't want to guess as to what the cause of the problem is but it is somewhere outside the editor itself and would appear related to disk access.

Just closing the loop on this issue in case others encounter it. I had some private chats with Michael from SoundQuest who suggested that the DLL error may be hardware related. Since the computer was still under warranty, I was able to get a replacement HD. After installing the HD (with a fresh installation of Win7), I no longer receive the error message. Of course, I can't say for certain what was actually causing the error in the first place. But it now works, so I'm happy. Many thanks to Michael for his help.

One random thought? Could it be that an anti-virus program possible tagged it and quarantined the needed file accidentally?

I just quit trying to make
it work.

navydave wrote:One random thought? Could it be that an anti-virus program possible tagged it and quarantined the needed file accidentally?

That is certainly a possibility, but not one that I explored. It seems to be running fine with the new drive and/or installation of Windows 7. I chose a new anti-virus this time (for no specific reason) so I can't compare.