Bc2000 (for the BCF2000 & BCR2000)

Hello everyone, 
i´m new here, and first of all, please excuse my englisch, it´s not my native language.
I got my BCR2000 used, and i´m new to that MIDI stuff, but i keep trying. 
Here´s my Problem: i wanted to upgrade the firmware from 1.04 to 1.10 using BC manager, and there were some dificulties resulting in my BCR showing "noOS". I already read somewhere here, that this is worst to happen, and i should read "BC MIDI Implementation.pdf" for help but i wasn´t able to find this file anywhere. After trying uploading the firmware again, there was a prompt saying: "no driver" or something like that. Trying to install a new driver failed too with the words: "This version of Windows is NOT supported! PLEASE CLOSE APPLICATION". 
This Device is frustrating. Really. What am i supposed to do now? I need help. 

thx

--- In bc2000@yahoogroups.com, "matschdreck" <matschdreck@...> wrote:
> I got my BCR2000 used, and i´m new to that MIDI stuff, but i keep
> trying. Here´s my Problem: i wanted to upgrade the firmware from 1.04
> to 1.10 using BC manager, and there were some dificulties resulting
> in my BCR showing "noOS". I already read somewhere here, that this is
> worst to happen, and i should read "BC MIDI Implementation.pdf" for
> help but i wasn´t able to find this file anywhere.

"BC MIDI Implementation.pdf" is at mntn-utils.110mb.com (which unfortunately is currently down - see my other post). However, in your specific case this document isn't much help anyway.

But have you looked at my message "Re: New BCF2000 Owner, Almost Totally Lost" (no. 1698, Sun Oct 19, 2008)? (Obviously, "Step 2" doesn't apply to your BCR.)

I'm a bit confused about what you're saying:
Have you actually used BC Manager to upload firmware vs. 1.10? If so, I'm a bit curious what happened, causing you to get "noOS" afterwards. Was the upload procedure somehow interrupted?

You may have to refer to the warning message in BC Manager's manual (section 8, under "MIDI -> Maintenance -> Send firmware") about the BCR's Operating Mode required during firmware upload.

> After trying uploading the firmware again, there was a prompt saying: "no driver"
> or something like that.

When the BCR is in "noOS" mode, its USB connection doesn't work at all: you must then use a "standard" MIDI connection (e.g. to your computer's sound card) to upload the firmware.

   Mark.

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:

> But have you looked at my message "Re: New BCF2000 Owner, Almost Totally Lost" (no. 1698, Sun Oct 19, 2008)? (Obviously, "Step 2" doesn't apply to your BCR.)

No, i didn´t read this message. Thanks for the hint. But as you said, i can´t perform "step 2", or actual anything on BCR at the moment. 
 
> I'm a bit confused about what you're saying:
> Have you actually used BC Manager to upload firmware vs. 1.10? If so, I'm a bit curious what happened, causing you to get "noOS" afterwards. Was the upload procedure somehow interrupted?
> You may have to refer to the warning message in BC Manager's manual (section 8, under "MIDI -> Maintenance -> Send firmware") about the BCR's Operating Mode required during firmware upload.

Yes, thats exactly what i did. I also checked up the BC Manager´s Manual Part you mentioned ("MIDI -> Maintenance -> Send firmware") BEFORE i tried, and i chose to set the Operating mode to U-1. And yes, the upload procedure was interrupted.
Unfortunately, i was to anxiuos to finish, and didn´t memorize the error prompt that occured. But the prompt told, that if i start the BCR again, it will just continue to work with the old firmware again, so i didn´t worry. I remember the prompt telling something in conjunction with the number 5 (or perhaps 8). Maybe "Error, preset 5 is not accepting..." sorry i can´t remember. I also watched the BCR during the upload procedure, and i could see the display somehow counting up, 1 -> 2 -> 3... etc, and when it came to 5, thats where the error prompt came. BC Manager also told me to look at the BCR Manual, and solve the problem before trying again, but i didn´t even understand the problem. I wonder if this information is helpful at all.

> When the BCR is in "noOS" mode, its USB connection doesn't work at all: you must then use a "standard" MIDI connection (e.g. to your computer's sound card) to upload the firmware.

I guess i will have to do this with a different computer. I dont have a MIDI connection, just laptop with usb. But i know a friend. Is there something i should be aware of, uploading this way? 

thanks for the answer Mark.

--- In bc2000@yahoogroups.com, "matschdreck" <matschdreck@...> wrote:
> yes, the upload procedure was interrupted. Unfortunately, i was to
> anxiuos to finish, and didn´t memorize the error prompt that occured.
> But the prompt told, that if i start the BCR again, it will just
> continue to work with the old firmware again, so i didn´t worry.

First some background explanation:
When you switch the BCR on, the BCR first checks whether the firmware on its EEPROM chip is valid, by means of a checksum.
If the firmware checksum is correct, the BCR copies the firmware from its EEPROM chip to its RAM, and then starts running from the RAM copy.
However, if the checksum is INcorrect, the BCR ignores the EEPROM firmware and enters the very basic "noOS" mode: of course this is typically the case if the previous upload procedure was interrupted, because the EEPROM firmware then consists of two unmatched parts (new + old).

So after a partial firmware upload, the BCR only keeps working with the old firmware (i.e. the RAM copy!) as long as you don't switch it off. (This is particularly relevant for the USB code.)
So what you could have tried (after the error message) was to repeat the uploading procedure BEFORE switching the BCR off (or meddling with the Windows USB driver software).

> I also watched the BCR during the upload procedure,
> and i could see the display somehow counting up, 1 -> 2 -> 3... etc,
> and when it came to 5, thats where the error prompt came. BC Manager
> also told me to look at the BCR Manual, and solve the problem before
> trying again, but i didn´t even understand the problem. I wonder if
> this information is helpful at all.

The number should run from 2 to 17. I have no idea where the error came from.

> I guess i will have to do this with a different computer. I dont have
> a MIDI connection, just laptop with usb. But i know a friend. Is
> there something i should be aware of, uploading this way?

In general there are 2 firmware upload methods:

A. Bidirectional.
This is what BC Manager's "Send firmware" routine does. In this case you'll need to connect the sound card to the BCR's "MIDI IN" and "MIDI OUT A" ("MIDI OUT B" is completely dysfunctional).

B. Unidirectional.
You can use any computer program capable of opening the firmware syx file and sending it via MIDI. So e.g. BC Manager, MIDI-OX, or even "MIDI Tools" (also downloadable from mntn-utils.110mb.com - once it's back on air...). Obviously, in this case you only need to connect to the BCR's "MIDI IN".
E.g. in BC Manager and MIDI Tools:
1. Open the MIDI System Exclusive messages window via the main window's View -> MIDI -> System Exclusive messages.
2. Open bcr2000_1-10.syx by executing File -> Insert.
3. Execute Edit -> Select all.
4. Execute Play.

I suggest you first try method A. If that somehow still fails, try method B.

Good luck!
   Mark.

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:

> So what you could have tried (after the error message) was to repeat the uploading procedure BEFORE switching the BCR off (or meddling with the Windows USB driver software).

I did! I repeated several times, it was always the same error. I tried to figure out what else could be done before i switched it off. I just didnt think it could be that bad then. I learned. 


> In general there are 2 firmware upload methods:
> 
> A. Bidirectional.
> This is what BC Manager's "Send firmware" routine does. In this case you'll need to connect the sound card to the BCR's "MIDI IN" and "MIDI OUT A" ("MIDI OUT B" is completely dysfunctional).
> 
> B. Unidirectional.
> You can use any computer program capable of opening the firmware syx file and sending it via MIDI. So e.g. BC Manager, MIDI-OX, or even "MIDI Tools" (also downloadable from mntn-utils.110mb.com - once it's back on air...). Obviously, in this case you only need to connect to the BCR's "MIDI IN".
> E.g. in BC Manager and MIDI Tools:
> 1. Open the MIDI System Exclusive messages window via the main window's View -> MIDI -> System Exclusive messages.
> 2. Open bcr2000_1-10.syx by executing File -> Insert.
> 3. Execute Edit -> Select all.
> 4. Execute Play.
> 
> I suggest you first try method A. If that somehow still fails, try method B.
> 
> Good luck!
>    Mark.

I´ll try that as soon as i get the possibility connecting via MIDI. Again, thanks for the help. 
Maciek

> --- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@> wrote:
> 
> > In general there are 2 firmware upload methods:
> > 
> > A. Bidirectional.
> > This is what BC Manager's "Send firmware" routine does. In this case you'll need to connect the sound card to the BCR's "MIDI IN" and "MIDI OUT A" ("MIDI OUT B" is completely dysfunctional).
> > 
> > B. Unidirectional.
> > You can use any computer program capable of opening the firmware syx file and sending it via MIDI. So e.g. BC Manager, MIDI-OX, or even "MIDI Tools" (also downloadable from mntn-utils.110mb.com - once it's back on air...). Obviously, in this case you only need to connect to the BCR's "MIDI IN".
> > E.g. in BC Manager and MIDI Tools:
> > 1. Open the MIDI System Exclusive messages window via the main window's View -> MIDI -> System Exclusive messages.
> > 2. Open bcr2000_1-10.syx by executing File -> Insert.
> > 3. Execute Edit -> Select all.
> > 4. Execute Play.
> > 
> > I suggest you first try method A. If that somehow still fails, try method B.
> > 
> > Good luck!
> >    Mark.
> 

Hello, just wanted to reply, i did it as suggested the first way. Everything went good, and it works fine now. Perfect!