Bc2000 (for the BCF2000 & BCR2000)

ok i went through the steps in the bottom half of this post http://launch.dir.groups.yahoo.com/group/bc2000/message/3856 to try to get that file for you but maybe im doing something wrong. heres my steps:

installed midi tools, downloaded BCF_Get_Firmware.syx
opened up midi tools, options, midi devices - under input/output tabs i have "BCR2000[1]" enabled (should it look like this? with another usb port it says "usb audio device"...) under both tabs (should i select this as thru devices also?)
then i press record under midi input messages, select "BCR2000[1]" as output device under midi system exclusive messages, insert BCF_Get_Firmware.syx under file, edit->select all and press play but nothing shows up on the midi input messages window. tried clicking stop and saving anyway but still nothing. any ideas?

--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "patrick_koondial" <patrick_koondial@> wrote:
> > im using winxp pro sp3 32 bit
> 
> OK, so then you have a wide choice of USB drivers.
> However, my personal favorite for XP is the Behringer 1.2.1.3 driver.
> I particularly like the very informative MIDI I/O port name scheme used by 1.2.1.3.
> For further discussion of all the available USB drivers, see section 4.4 of the BC Manager Manual (downloadable from http://home.kpn.nl/f2hmjvandenberg281/bcman.html).
> 
> > using the update utility and firmware from behringers site causes the update utility to close immediately after opening the firmware update for 1.10 
> 
> Ah, yes: I could never get Behringer's update utility to work either.
> (See section 4.2 of the BC Manager Manual.)
> 
> Instead, you can use any program capable of uploading System Exclusive messages.
> If you want to use my own BC Manager, see "Send firmware" on p. 38 of the BC Manager Manual.
> 
> The most important thing to remember (no matter which program you use):
> 
> If the firmware upload process is somehow interrupted, you should NOT switch the BCR off, because then after switching it on again, the BCR's display will say "noOS" and you'll have to retry uploading the firmware in an S-mode, which means that you can't use the USB connection, but only the BCR's "real" MIDI input port.
> (That's because the BCR's USB support is IN its current firmware - so if the firmware is trashed (i.e. partly overwritten), you are left with only the always-present bootloader, which only supports the standard MIDI input port.)
> 
> So instead, if the upload process is interrupted, you should simply redo the upload process, until it goes well. (The BCR's "old" USB connection will remain operational until you switch the unit off.)
> This is one of the reasons why BC Manager's upload routine is very safe: it works bidirectionally and can thus tell you whether the upload has been complete.
> 
> > i installed the most current driver from behringers site (USB MIDI Driver 32-bit USB MIDI Driver). i just uninstalled and installed 1.2.1.3 so this may work
> 
> Great! And now you can blame ME if it doesn't...
> 
> > im waiting to try upgrading firmware so i can try this process. thanks for uploading the file i will try once im off work 
> > 
> > thanks for all your help. i will try all this tonight and get back to you as soon as i can.
> 
> Good luck!
> Mark.
>