KeithL
Administrator 
Posts: 10,256
Member is Online
|
Post by KeithL on Apr 22, 2016 11:59:27 GMT -5
FALSE POSITIVE  Unfortunately, the problem is a faulty virus definition in the Symantec database that yields a false-positive. I'm not sure if it's a actual faulty signature, or just a "heuristic analysis" that's too aggressive, but the fault is on their side and not ours. ( THE ERROR IS THEIRS, and it's up to them to correct their virus definitions to eliminate the error. Although, if you were to actually contact their support folks, I suspect they'll just tell you to ignore it.) Note that, if their problem is only with the installer, and not with the drivers themselves, then you should be able to disable Symantec, install the drivers, then re-enable Symantec. While I am very confident that there is not Trojan in the driver file, but I'm just disappointed about this. It's been more an a year and there's no fixing the issue of detected Trojan. Don't get me wrong, I got lots of emotive products running at my place. But for this issue, it's just an inconvenient and it reduces the customer experience. I bought the big ego with a full intention to use it at work. While using UAC1 mode works, but every time I restart the computer, I would have to unplug the big ego and plug it back to run it as UAC1 mode. I tried installing the driver of course. The Trojan issue made it impossible for me to use UAC2 mode. I was not able to deactivate my antivirus at work, nor that is an option. I just felt that if emotive wants to compete with the big boys, then customer service and user experience got to step it up. Yes, there's no Trojan on the driver. But if a product requires the customer to jump through hoops to make it work, I wouldn't call that a satisfactory customer experience. Just some feedback. Is it Symantec's antivirus program?
|
|
KeithL
Administrator
Posts: 10,256
Member is Online
|
Post by KeithL on Apr 22, 2016 12:05:18 GMT -5
FALSE POSITIVE Unfortunately, the problem is a faulty virus definition in the Symantec database that yields a false-positive. I'm not sure if it's a actual faulty signature, or just a "heuristic analysis" that's too aggressive, but the fault is on their side and not ours. ( THE ERROR IS THEIRS, and it's up to them to correct their virus definitions to eliminate the error. Although, if you were to actually contact their support folks, I suspect they'll just tell you to ignore it.) Note that, if their problem is only with the installer, and not with the drivers themselves, then you should be able to disable Symantec, install the drivers, then re-enable Symantec. Unfortunately, I can't really do much to help you if your employer has made this option unavailable. (And we included driverless mode just to cope with such situations.) Is it Symantec's antivirus program? |
|
|
|
Post by geebo on Apr 22, 2016 12:06:02 GMT -5
FALSE POSITIVE Unfortunately, the problem is a faulty virus definition in the Symantec database that yields a false-positive. I'm not sure if it's a actual faulty signature, or just a "heuristic analysis" that's too aggressive, but the fault is on their side and not ours. ( THE ERROR IS THEIRS, and it's up to them to correct their virus definitions to eliminate the error. Although, if you were to actually contact their support folks, I suspect they'll just tell you to ignore it.) Note that, if their problem is only with the installer, and not with the drivers themselves, then you should be able to disable Symantec, install the drivers, then re-enable Symantec. Is it Symantec's antivirus program? This is what I was suspecting, Keith and it's why I asked if it was Symantec that was giving the false positive to user tungx2. If Symantec is reporting trojan code in a legitimate driver it's on them to correct the error. |
|
|
|
Post by Tungx2 on Apr 22, 2016 13:52:44 GMT -5
yes it was, unfortunately. I guess these guys get a lot of commercial contracts
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 21, 2016 9:35:35 GMT -5
While I am very confident that there is not Trojan in the driver file, but I'm just disappointed about this. It's been more an a year and there's no fixing the issue of detected Trojan. Don't get me wrong, I got lots of emotive products running at my place. But for this issue, it's just an inconvenient and it reduces the customer experience. I bought the big ego with a full intention to use it at work. While using UAC1 mode works, but every time I restart the computer, I would have to unplug the big ego and plug it back to run it as UAC1 mode. I tried installing the driver of course. The Trojan issue made it impossible for me to use UAC2 mode. I was not able to deactivate my antivirus at work, nor that is an option. I just felt that if emotive wants to compete with the big boys, then customer service and user experience got to step it up. Yes, there's no Trojan on the driver. But if a product requires the customer to jump through hoops to make it work, I wouldn't call that a satisfactory customer experience. Just some feedback. Keep in mind, the problem here is not with the Emotiva Ego drivers at all, but with Symantec and your company's overzealous virus scanning settings, which are impairing your ability to use your work computer. In your initial post, you said that Symantec Antivirus was detecting the item as "Trojan.Gen.SMH", and a quick google search of that term leads to a Symantec article saying that this detection isn't referring to any "known" type of trojan, but just a file that Symantec thinks is a trojan of "unknown type" - which means that it is actually a false positive, not giving any reason to suspect the driver contains any actual malicious code at all. We can't do anything about this, since we don't know what it is about our driver installation that Symantec thinks is a threat. The only workable resolution is to add the driver to the list of exceptions that the virus scanning program will not block. This issue could just as easily affect driver installation programs from any number of manufacturers using the same USB chipset as ours, or even other chipsets. This issue requires resolution with your office IT personnel; there isn't any obvious 'fix' we could make to our driver installer to avoid this. |
|
|
|
Post by cullenhall on Jul 19, 2017 13:05:54 GMT -5
With some help from Keith (a few months ago - its been busy) he provided me the raw .sys and .dll files that make up the drivers for the little EGO. windows (in my case 7) was upset because there was not an .inf file to help tell windows which files to get and where to put them (my simpleton understanding of what a .inf file does with respect to drivers) I installed the drivers on an older XP computer and found the .inf file on that machine. I combined all those files into one folder. Now if I tell windows that I have the disk and I point it towards the "EmotivaUSB20ks.inf" file sure enough my little ego starts to work at all sample rates. I don't have the nice Emotiva app and volume control but it works. I am not sure if I am controlling the ladder resistor network volume control but its working. The folder that I combined everything into is attached in a .zip. hopefully it helps someone. If I get the Emotiva app volume control working ill be sure to update. |
|
|
|
Post by cullenhall on Jul 19, 2017 13:10:58 GMT -5
This is the message I get when I attempt to run the Emotiva app. Anyone have any idea what .DLL it is looking for and where to put it? Attachments:
|
|
KeithL
Administrator
Posts: 10,256
Member is Online
|
Post by KeithL on Jul 19, 2017 13:28:24 GMT -5
Unfortunately I've never seen that particular error before. This is the message I get when I attempt to run the Emotiva app. Anyone have any idea what .DLL it is looking for and where to put it? |
|
|
|
Post by cullenhall on Jul 19, 2017 13:30:52 GMT -5
Unfortunately I've never seen that particular error before. This is the message I get when I attempt to run the Emotiva app. Anyone have any idea what .DLL it is looking for and where to put it? I think its only because I didn't use the installer and just the Emotiva app .exe alone is looking for some .dll that I didn't bring over onto my windows 7 machine. |
|
KeithL
Administrator
Posts: 10,256
Member is Online
|
Post by KeithL on Jul 19, 2017 13:33:14 GMT -5
As far as I know, the fancy ladder network internal volume control is controlled via metadata passed by the player program. Also, as far as I know, the only player that currently supports this is jRiver Media Center. (There's some sort of standard for controlling volume via USB that this complies with.) jRiver offers three different volume control choices... and one of them utilizes the internal ladder volume control. (To be honest, a well-implemented digital volume control isn't really all that bad, so I really wouldn't worry about it.... ) With some help from Keith (a few months ago - its been busy) he provided me the raw .sys and .dll files that make up the drivers for the little EGO. windows (in my case 7) was upset because there was not an .inf file to help tell windows which files to get and where to put them (my simpleton understanding of what a .inf file does with respect to drivers) I installed the drivers on an older XP computer and found the .inf file on that machine. I combined all those files into one folder. Now if I tell windows that I have the disk and I point it towards the "EmotivaUSB20ks.inf" file sure enough my little ego starts to work at all sample rates. I don't have the nice Emotiva app and volume control but it works. I am not sure if I am controlling the ladder resistor network volume control but its working. The folder that I combined everything into is attached in a .zip. hopefully it helps someone. If I get the Emotiva app volume control working ill be sure to update. |
|
|
|
Post by Loop 7 on Jul 19, 2017 14:23:08 GMT -5
Naive question - the drivers for WIndows are solely to enable resolutions above 24/96 or are the drivers needed for everything above 16/44 plus other OS functionality like volume control, etc?
|
|
KeithL
Administrator
Posts: 10,256
Member is Online
|
Post by KeithL on Jul 19, 2017 15:03:21 GMT -5
The drivers are really only necessary to enable toe DAC to handle sample rates above 24/96k. The EGO DACs have two operating modes: UAC1 (driverless) - which supports up to 24/96k UAC2 (drivers) - which supports up to 384k The only slightly annoying part is that the UAC2 mode is the default - and to switch to UAC1 driverless mode you have to hold the button down while plugging in the DAC. Since the DAC doesn't remember which mode it's in, if you turn the computer off and back on again, while leaving the DAC connected, and don't hold the button down, the DAC will wake up in UAC2 mode. In order to get it to wake up in driverless mode you have to hold that button down while you turn on the computer. (Or unplug the DAC, then plug it back in while holding the button down, to switch it back to UAC1 mode.) It was set up this way because we figured you'd use the drivers most of the time - and only want to avoid them when using the Ego with a friend's computer, or one at your local library. Therefore, we set things up so there was no way to get the DAC to always start up in driverless mode, since we figured most people would only do so occasionally. Naive question - the drivers for WIndows are solely to enable resolutions above 24/96 or are the drivers needed for everything above 16/44 plus other OS functionality like volume control, etc? |
|
|
|
Post by cullenhall on Jul 19, 2017 17:06:46 GMT -5
ok so I got things fully working as if I had run the "install the EGO drivers.exe" file had been run (the one that keeps getting flagged by Symantec).
here is a breakdown of the steps that worked for me on a corporate windows 7 64-bit machine:
1. Download the .zip file I posted earlier that has EVERYTHING that you need to get this going.
2. Unzip that folder and place the contents at "C:\Program Files\Emotiva Audio\Emotiva USB 2.0 Audio Driver"
3. Go do device manager and select the EGO that does not have drivers assocaited with it, I think its called "Emotiva Little EGO" or whatever device you happen to have
4. Right click and do "update driver software..." and select the "Browse my computer for driver software" option
5. In the "search for driver software in this location:" section browse to "C:\Program Files\Emotiva Audio\Emotiva USB 2.0 Audio Driver" and select that folder then hit next
6. Windows should find and install the right drivers
7. Your EGO should now appear as a sound card and work - except....
8. You will notice the "Emotiva" icon is missing from the task bar - this bugged me i guess so I did some digging using the "tasklist /m" command in command prompt and i found that the Emotiva app only (apparently) needs one .dll that is not native to windows and it is called "EmotivaUSB20api.dll"
9. You will need to register this .dll with windows, to do this open a command prompt and type the following: "regsvr32 "C:\Program Files\Emotiva Audio\Emotiva USB 2.0 Audio Driver\EmotivaUSB20api.dll"" and hit enter
10. it should give you some kind of prompt telling you that you have registered the .dll
11. and if you click on the "EmotivaUSB20ControlPanel.exe" (what I have been calling the app) it should launch
12. Add a shortcut to "EmotivaUSB20ControlPanel.exe" in the statup menu and you should be good to go.
|
|
|
|
Post by just me on Feb 13, 2018 21:07:15 GMT -5
Is there a link that works for the windows drivers? I cannot find one.
|
|
KeithL
Administrator
Posts: 10,256
Member is Online
|
Post by KeithL on Feb 14, 2018 10:26:52 GMT -5
|
|
|
|
Post by thepatriot on Feb 14, 2018 16:27:08 GMT -5
Thank you, Keith, for the links. I'm looking for a DAC and the Big Ego is one of the two that I'm looking at with the Dragonfly Red being the other. I will be making up my mind soon.
|
|
While I am very confident that there is not Trojan in the driver file, but I'm just disappointed about this. It's been more an a year and there's no fixing the issue of detected Trojan.
