Emu XL-7 & MP-7 User's Group

Glad you got that ironed out. The info and file will come in handy for
those with version 1.0 or anyone running into a snag while trying to
update. I would like to thank realm for his FAQ. That is where I read
about eloader not supporting USB for updating the OS which I mentioned
in a previous reply to you. Hope the OS update takes care of the
issues you were having.

DigiD

--- In xl7@yahoogroups.com, "tcdave" <davedude_92692@y...> wrote:
> Well Boys and Girls,
> 
> We can put this topic to rest.  Today I called EMU and they told me 
> since I had version 1.0, I had to install a preparation program in my 
> XL7 BEFORE I install version 2.0.  This program "preps" the machine 
> to go to version 2.0.  Weird.  Anyways, the file is 
> called "commandprep10.dli" and you install it just like an operating 
> system on eloader.  If you are looking for this file, you can't get 
> it.  They had to email it to me and its not on the EMU website.  I 
> will try to upload to this message board's files.
> 
> Anyways, I tried to download it into the XL7 and for some reason 
> the "Prep" program couldnt download.  So I called EMU again and 
> determined that is was my MIDI connection.  They also recommended 
> that I get 2 new high quality MIDI cables.  The thin ones won't do 
> (like the free guitar center cables)  ALSO, EMU said not to have the 
> USB hooked up AT ALL.  And they was right.  Both the "Prep" Program 
> and the XL7 OS V2.0 got corrupted somehow since I had the USB 
> connected.  Thru ALOT of troubleshooting on my own, I found this 
> out.  So, leave the USB connection OFF.  I then reloaded the prep 
> program, and it worked!  Finally, I downloaded the OS to the XL7 and 
> was successful.  
> 
> One last thing, I was using the MIDIMAN MIDISPORT 4X4 USB MIDI 
> interface and found out that "A" MIDI IN port worked but MIDI OUT 
> didn't.  Also, both "B" MIDI IN/OUt port and "C" MIDI: IN/OUT port 
> didnt function at all.  The last "D" IN/OUT port worked perfectly for 
> this.  It is important that both MIDI IN and OUT works perfectly in 
> whatever MIDI interface you have.
> 
> My next call?  To MAudio to check out why my MIDISPORT does'nt 
> completely work.  
> 
> Wow, what a weekend!
> 
> tcdave
> 
> 
> PS - in regards to the Device ID, EMU said it has nothing to do with 
> downloading the OS.  The OS is downloaded ONLY thru MIDI.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
> wrote:
> > --- In xl7@yahoogroups.com, "tcdave" <davedude_92692@y...> wrote:
> > > One more thing, I read on this message board soemwhere that the 
> > Sysex 
> > > Device ID is 010.  But the info in the readme file says 
> (default=0)
> > > 
> > > I tried both "0" and "010" and neither work...
> > > 
> > > tcdave
> > > 
> > 
> > F0 18 0F 00 55 . . . F7
> > F0 18 0F ID 55 . . . F7
> > 
> > So far as I've seen, the E-Mu Command Station midi sysex device ID 
> (0-
> > 126) refers to the specific ID you have a particular piece of gear 
> > set to.  The theory is this: if you have multiple units of a 
> > manufacturer's gear, you can target sysex messages to specific 
> units 
> > by having each set to a different ID.
> > 
> > If you are still trying to install OS2.0, I'm not sure device ID 
> > makes a difference.
> > 
> > Hope this helps.
> > 
> > Dr. Steve