Comments on: Korg MS2000 Bricked by Firmware Update

By: John Keston

John Keston — Thu, 02 Feb 2012 04:50:28 +0000

Scary thinking you might have a bricked instrument, eh? Congrats on getting it working!

By: Tim Brown

Tim Brown — Tue, 31 Jan 2012 05:07:05 +0000

Wow, I just went to hell and back with this issue! I had a problem updating my MS2000 from V1.03 to 1.07. I followed the above advise but didn’t have another midi interface to work with. I ended up downgrading my m-audio driver back to around 2003 and it worked… I was running Delta_6_0_2_5_10_0_5074 on XP SP3 for the better interface, but tried Delta_WDM_5_10_00_5057v3 and it worked… Phew! I ran it in slow just to be sure… I have since gone back up to the newer driver and everything seems fine again and I have V1.07 :) ps. when the instructions say remove maudio product with computer on, I just took the cable out of the back of the computer, I didn’t want to remove the card inside with the computer running!!

By: John Keston

John Keston — Mon, 11 Jul 2011 17:50:01 +0000

That’s a good question. I thought it might help with some of the aliasing I was getting in the filter and choppy external sync, but it made no difference. I’m sure there’s bug fixes of some sort. Please chime in if you find details.

By: CalB

CalB — Sat, 09 Jul 2011 23:55:10 +0000

what does the ms2000 upgrade do? I wanna try it but the crash thing is wiggn me out

By: ath

ath — Wed, 01 Sep 2010 03:05:17 +0000

I had a problem updating my MS2000 from V1.04 to 1.07. The Win XP Midi reg entry fix didn’t resolve the issue. I was recieving the following error regardless of what transfer speed I chose in the Korg Updater app:

“The MS2000 returned a bad message.” <— or something similar.

I was using a CME USB to MIDI cable (CME U2MIDI). I ended up installing Windows 7 onto my laptop and used the Windows Vista driver for my USB/MIDI cable which I downloaded from CME's website and performed the transfer again and it worked fine. CME don't provide a WINXP driver for this cable on their site, because XP uses the Microsoft Plug and Play driver for the cable. This may have been where the issue lied, just thought I'd post this here in case anyone else finds themselves in a similar situation as I couldn't find this issue or the above error message documented anywhere on the web, hope this is of some use to someone. I'm now rocking v1.07 on my MS2000.

Cheers,

ath

By: John Keston

John Keston — Thu, 25 Mar 2010 17:20:47 +0000

Utility from M-Audio that automatically fixes the registry:
http://www.m-audio.com/index.php?do=support.drivers&k=driver&s=8&o=%20Windows+XP&f=84

By: GB

GB — Thu, 25 Mar 2010 14:44:50 +0000

What utility did you use to clear the registry?

By: John Keston

John Keston — Sat, 20 Mar 2010 15:19:57 +0000

Thanks Grant and Trainspotter. I have brought it back to life. Seems I was a victim of the 10 MIDI entry limit in XP. Odd thing is that manually deleting the entries in the registry then applying the update with my M-Audio FireWire 410 didn’t work. However when I used the utility to clear the entries and swapped the 410 with a Midisport 4×4 it did. I think there’s got to be a bug in the MIDI support for the 410. I have had midi sync problems with it too.

By: Grant Muller

Grant Muller — Thu, 18 Mar 2010 14:57:51 +0000

Ooooooh! Sorry John I thought you were doing this with a Mac! I’m actually well aware of that shortcoming with Windows XP…I would have pointed that out.

Let us know if that actually works.

BTW, MIDI-OX, the tool trainspotter mentioned is invaluable for tracing MIDI problems on Windows. If you’re still having trouble you might capture a log with that and post it up here.

By: trainspotter

trainspotter — Wed, 17 Mar 2010 18:02:46 +0000

http://www.midiox.com/?http://www.midiox.com/moxdown.htm