MS2000 crash on upgrading operating system - help

[Sparker]

I updated my MS2000 operating system from 1.03 to 1.07 using the Korg support site update download.
The update got 1/2 way through and crashed.
When I turned the MS2000 back on the is no startup screen just a lot of lines/symbols. I've tried the factory initialise reboot but no joy.
Tried the update utility several times but keep getting error messages saying that MS2K is not sending midi to the PC.
I suspect that I may have had the MIDI send turned to 'disable' when I ran the update utility, (no warning in the update instructions if this is the case)

Does anyone know how to restore MS2K to its initial operating system from a cold boot/power on?

[Daz]

Hey Sparker,

There is no way to do that other than completing the OS update using the updater app, but I am pretty confident this can be fixed.

A few things to try (some obvious, forgive me, and others less so)

1) Confirm you've really wired both MIDI IN and OUT on the MS2K to MIDI OUT and IN respectively on your MIDI interface
2) Ensure you have the latest drivers for your MIDI interface. Sometimes older drivers on some brands drop sysex data (aaargh !)
3) In the Configuration of the updater, set the Data Transfer Rate to a slower speed than the default "Very Fast"
4) Be sure to set the option Skip Version Check, as your half updated MS2K might be reporting the wrong version to the updater and stopping it from doing the update.
5) Let us see the contents of your vup_log.txt, that might indicate what the problem is here.

That's all I can think of for now ...

Daz.

p.s. I know a fair bit about this subject, but I am not part of Korg or their support (just an MS2K user like yourself), so talking to Korg support should probably be on that list of things to do too. Try what I have said first though.

[Sparker]

Hi Daz
Thanks for the fast reply.
I think you gave me a checklist of all I did.
I've already installed the lastest updates to the M-Audio soundcard and it runs my triton fine.
I connested up another MIDI device (Korg ESX) and checked that the MIDI in out was functioning through the soundcard. (The one thing I havn't done on this soundcard is transmit sys.ex messages - still a step further than I've gone in the past with MIDI data).
I checked the log and saw that I reported that the system had been updated from the first attempt I made so reasoned that the version check was preventing a straight data dump, so I disabled the version check. The first time I ran the updater I noticed that the first four of the sequencer lights had come on. So I ran the updater at progressively slower speeds. After the last run the first 7 lights had come on, but no further since.
I've tried various cold boots using the WRITE key in conjuction with the SEQ MOD key pressed and various of the sequencer keys. The only english charatures that came up was when I pressed WRITE, SEQ MOD and seq button 4 - the creen said 'reg.)
When I turn the MS"K on I just get a series of I shaped charactures and a huge comma type characture. When I press WRITE MOD SEQ and button 5 I get a string of non english symbols.
I suspect that I didn't enable the MIDI out screen and that the update requires 2 way communication with the updater on the laptop. (I was surprised as I thought that the compiler would just drop a full operating system into the MS2K. (My triton booted its upgrade ops sys from off the data storage card without needing to interface with the PC)
I have written to Korg UK support as they have given excellent tech advise in the past. However I'm now kicking myself as I wrote via the Korg tech enquiry web form, which means I have to wait three days before contacting them again. (Kicking myself 'cause I found my direct line phone number to the tech workshop and could probably have got a solution right off.)
I'm hoping that theres some way of reactivating the onboard chips default operating system, (ig it has one) from a cold boot. Otherwise I guess I'll have to send it in to the repair depot. I've done this twice in the past with my triton and they have been excellent - best customer and tech suport I've ever had IMHO.

If you've any further suggestions they are more than welcome. I only picked it up as a private purchase yesterday and had given it a thorough workout to check that all the pots, buttons and screens checked out before I did the upgrade. So I was looking forward to getting stuckin with the patchbuddy to reload all my fav patches from the last MS2K I had.
(You can tell how twiddling my thumbs I am from the length of this post.

I've got the log from the updater, which I'll post into my next post as its getting faily long.

All the best

Sparker

[Sparker]

Hi
Her's my log file from the updater:


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows 2000 (Service Pack 4)
****************

****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : No
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending version check...

Version check successful.

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : No
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending version check...

Version check failed. Same version or better.


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : No
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending version check...

Version check failed. Same version or better.


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Update failed : Receive Error(Timeout)

User aborted update


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Slow
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Fast
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Rx Msg Error(4:Msg Code Error)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Slow
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Slow
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Update failed : Receive Error(Timeout)


****************
** MS2000/R SystemUpdate Utility v1.3 started on Microsoft Windows XP (Service Pack 3)
****************
Starting MIDI transfer of file C:\Documents and Settings\Maxdata\My Documents\My Data\Korg\MS2K\MS2K Operating System v.1.07\MS2000_V107\x811v107.sys
SkipVer : Yes
XferRate : Very Slow
MidiOut : FW AP MIDI v5.10 (0x50a)
MidiIn : FW AP MIDI v5.10 (0x50a)

Sending 'Set Mode'...

Set Mode successful.

Update failed : Receive Error(Timeout)

[Daz]

Hi Sparker,

Damn ... you were already hot on diagnosing the problem

The updater software does just seem to be timing out waiting for a reply to the sysex packets it is sending to the MS2K.

FWIW, the way the updater works is pretty simple. It sends the OS update in chunks. Each chunk is a sysex message and the updater expects an ACK for each chunk before it sends the next. Fat sysex messages really put your MIDI interface to the test, so if you're 5000% percent sure you've cabled it up right I'd try the following :

1) Try another MIDI interface if you have access to one, or maybe some one else's PC

2) If it is USB based make sure the MIDI I/F is not plugged into a hub and disconnect all other USB peripherals.

3) Ensure no other instruments are attached to your MIDI interface during the update, especially ones that might be sending clock or active sensing.

NOTE: just spotted the fact that the log reads :

"Sending version check... Version check failed. Same version or better. "

That confirms you have it cabled up correctly Ignore my comment above.

I do have my own "unofficial" OS update package which I devised for Mac users. It contains just the raw sysex messages and they can be sent sequentially using an MIDI sysex sending app, allowing a manual OS update.

My 2p,

Daz.

[Sparker]

Hi Daz
I've got another desktop PC in my studio running through a Edirol/Roland UR-80 soundcard, (the one with the mixer inerface)
I used this one when I configured my original MS2K.
Its running thorugh a hub at the mo. I'll try it direct into the PC.
I'll have to wait till tomorrow tho, as its coming up mid-night here and my studio is at the bottom of the field!

I have a growing suspision that I'll be posting to the Korg depot, unless the chip can be reset from here - (I'm not even sure that the chips work like that - having some sort of basic OS built in - maybe they're blank till something gets written into them.)

Thanks for all the advice. Just been trawling some of the posts and finding an impressive amount of posts from yourself.

cheers
Sparker

[Daz]

IIRC there is a basic OS burned into the ROM of the MS2K, but it does very little other than handle this OS update via MIDI; writing what it gets to the flash RAM that holds the actually main OS.

Let me know how you get on tomorrow. You know where I am if you need any more help

[Sparker]

Hi
I've got it sorted out.
I contacted Korg support and technical services and they sent me an article in pdf format about a problem with Window XP and the midi drivers in the registry system.
In XP Windows only allows ten midi drivers, any more and additional devices won't utilise their drivers, (even they show as loaded).
The answer is to go windows registery and delete any drivers that have been duplicated. HOWEVER this is risky stuff as changing the registery can cause a major system crash needing the re-installation of the operating system.

I got around the problem by using another laptop which happened to be running Vista. I examined the Vista registery and it looks to me as if Vista organises it's MIDI registry drivers in a differnt way. (I.e. I couldn't find their location!)

I ran the MS2K updater on vista and the 1.07 operating system loaded onto my MS2K.

I don't know if it's possible to attach pdf files to threads in this forum. If it is let me know how and I'll post the article on XP and the midi registry limitations.

It does stike me that with more people adding midi devices and the fact that most/many music programmes run on XP that this may be a growing problem. I haven't seen it mentioned in other threads, (but I'm new on the site)
In any event I've added the links below to sites that relate to this problem.

RME has an excellent FAQ on this subject by Matthias
Carstens at
http://www.rme-audio.de/en_support_tech ... q_10entryd

called "The 10 Entry Limit in Windows NT/2000/XP"

M-Audio offers a “MIDI Fix” utility at
http://www.maudio.com/index.php?do=supp ... driver&s=8
&o=Windows+XP&f=84.
This clears out previouslyinstalled
MIDI devices, as described in a text file included
with the utility, but you will have to reinstall the deleted
drivers manually.)

If you do want to edit the registry then its recommended that before making any changes you run this:
Microsoft’s instructions for registry backup at

http://support.microsoft.com/kb/322756/.

Thanks for all the help. Your suggestion of using another PC or soundcard was the right solution for my problem.

I'm probably going to tread carefully in the registry and see if I can remove some of my duplicated drivers - apparently whenever I tried to reload the soundcard drivers it just kepy adding the same driver again and again effectively using up all ten of my driver slots.

I suspect the same may also apply to the wavesys drivers in the XP registry.

best regards

Sparker

[ClintRubber]

Hello,

Before upgrading to 1.07 I was wondering if I could check which version
is currently in the MS2000. Was assuming such a thing could be displayed during startup, but it isn't.

Is there perhaps some magic button-sequence that shows the current version ?
(like for instance hold 'a certain button' while powering-up)

Thanks,

Peter

[wallstreet]

where's the OS for mac!

[X-Trade]

Hi
I've got it sorted out.
I contacted Korg support and technical services and they sent me an article in pdf format about a problem with Window XP and the midi drivers in the registry system.
In XP Windows only allows ten midi drivers, any more and additional devices won't utilise their drivers, (even they show as loaded).
The answer is to go windows registery and delete any drivers that have been duplicated. HOWEVER this is risky stuff as changing the registery can cause a major system crash needing the re-installation of the operating system.

...

the Windows MIDI limitation and how to fix it is widely documented on the web.

The idea that editing the registry is dangerous is misleading - it is preventing you from fixing a problem in that you won't at this point be able to install any other MIDI drivers successfully unless you do fix it.

Editing the registry itself is not dangerous and will not cause a system crash - it will only cause problems if you go around and mess with other parts of the registry that you aren't supposed to. As long as you keep to the instructions you will be fine.

There is some very important information for windows in the registry, which is why there are warnings about it. However, you shouldn't let that deter you if you have a problem and relatively know what you're doing, and you make sure you are deleting/editing the right keys as it says in the instructions.

I think what I'm trying to say is that you won't go and kill your PC simply by doing what it says in the instructions and removing unused MIDI devices. you will kill your PC if you stray off and go messing about with other things in the registry which is what the warnings are for.

[mikemolloyuk]

best customer and tech suport I've ever had IMHO.

Thank you.. Comments like this make all our efferts worth it..

Mike
Korg UK Tech Support

[ClintRubber]

Hello,

Before upgrading to 1.07 I was wondering if I could check which version
is currently in the MS2000. Was assuming such a thing could be displayed during startup, but it isn't.

Is there perhaps some magic button-sequence that shows the current version ?
(like for instance hold 'a certain button' while powering-up)

Apologies here for asking, the press ModSeq + [5] (IIRC) works fine. Just had a sticking ModSeq button.

[keston]

Anyone have a link to the alleged PDF from Korg to fix the bunged up firmware update problem?

Thanks!

[astronaut]

Apologies here for asking, the press ModSeq + [5] (IIRC) works fine. Just had a sticking ModSeq button.

Hi

where did you find out about this function? I can't seem to find it in the user manual...


I did check for the version of my MS2000R and it stated "My version is 05", so this means 1.05?

cheers