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

More thoughts and resources on:
=============================================
(1) Possible Java related issues
(2) USB Composite Devices 
=============================================
(1) Java

I don't know beans about Macs (or netbeams about Java), but maybe e-
loader's "private" copy of Java has been made non-operable by later 
Mac OSes. Here's what the e-loader 1.1 READ ME doc says:

E-Loader and Java
E-Loader requires Java, which is a programming toolkit that helps 
developers to rapidly construct sophisticated applications. One of 
the primary reasons E-Loader was developed using Java is because it 
is especially helpful in developing applications that must run on 
multiple operating systems. 

In order to simplify dealing with this dependency the default 
installation of E-Loader will automatically install a compatible 
version of Java that is private to E-Loader. By doing it this way we 
eliminate any possible incompatibilities with unsupported versions of 
Java or any possible interactions with other applications on your 
computer that also use Java. 

The downside to supplying a private copy of Java for E-Loader is an 
increased installer package size. The extra copy of Java adds about 
6MB to the installer package (making the entire package about 9MB). 
If you are downloading from the web over a slow connection this could 
be a problem. If you are getting the installer from a CD it should 
not be an issue. If you have a problem downloading a package of this 
size you should contact the E-mu Support Group and they can send you 
a CD via postal mail. 

If you are a sophisticated Java user and know about the differences 
between Java Runtime Environments and how to configure them or have a 
preference for a particular version, you may want to change the 
default way E-Loader is installed. We highly recommend against this 
if at all possible because it can be tricky to get it all correct and 
you may not get the stability and performance available from the 
version with the bundled Java, as this is what we test most. A 
description of how to manually install Java to work best with E-
Loader is available in a separate document. The E-mu Support Group 
can help with this type of installation, though they will not be able 
to describe and troubleshoot every possible Java installation option. 

=============================================
(2) USB Composite Devices 

I don't know beans about usb drivers and the whole enumeration 
process either, but I did research "USB Composite Device." The E-Mu 
CS/P2500 is a usb composite device.

First of all, the *.inf files for the E-Mu usb drivers confirm that 
the Hardware ID for my new USB Composite Device is for the E-Mu. I 
don't remember seeing it before and its not listed as a string in 
either of the *.inf files. So, I am wondering if is the result of an 
XP update/hotfix/SP. (Maybe someone with more computer understanding 
has an insight.)

Second, Microsoft has some info about problems with usb Composite 
Devices and Vista. Here's one: http://support.microsoft.com/kb/933442 
(A USB composite device does not work after you disable and then 
enable the device in Device Manager on a computer that is running 
Windows Vista)

Third, here are some other sites. (I only understand about 
1/1,000,000th of what they are talking about, but my instincts lead 
me to believe that the e-loader/usb issue is relate to this stuff. 
Any computer techies here make sense of all this?

http://www.microsoft.com/whdc/connect/usb/usbfaq_intermed.mspx [See 
section on composite devices]
http://www.cygnal.org/ubb/Forum9/HTML/001050.html

What little I do understand leads me to believe that there were 
changes in XP SP2 (and SP3) that changed the way USB Composite 
Devices are handled. If I am right, that might explain why I was able 
to install the E-Mu usb drivers on my XP.

Good luck; don't give up!!!

--Steve