Windows 10 and USB Gadget

So I think what is happening is that the InstallShield Version that the driver package was built with doesn't support Windows 10 fully. I confirmed that I the drivers didn't show up for me by installing the 2.3.2 Nomad version on my Windows 10 VM. I then took the driver installer package as built by our new version of InstallShield and the driver seemed to push into the system as expected. This is something that we will address in a future release.

In the mean time, as jpgagnon mentions you should be able to manually install the device driver through device manager from the Program Files\ETC\HighSpeed_Pipeline_Drivers location. If you need assistance with this process, please don't hesitate to reach out. We have an installer package that we could potentially make available as well to see if the new installer package would work for you.

worked fine under win10 for me, but had a problem with win7 professional...

Can you tell me more about the Win10 install that worked and the Win7 install that doesn't please?

installed 2.3.2 under win10, nomad dongle worked (although there was a problem with the permission for a certain part of the safenet drivers), gadget was recognized fine. no need to manually or re-install.
on a client's win7 professional setup, nomad installation of 2.3.2 looked like it was working. no error message (at least not a visible one). dongle was recognized, nomad would start. but it had no library. and when connecting a gadget i would get the error of unknown device. checked the hard drive and could find the pipeline driver in the ETC directory. installed manually, worked fine. for the missing library i downloaded the most recent library patch and installed it through the shell. worked fine after that.

there have been other reports about library missing after installtion of 2.3.2. don't know if here in the forum or in the facebook group

ETCnomad_Eos_PC_v2.3.2.9.0.45 was used on both?

Yes. On the win 10 PC I had a previous nomad version (not sure which, probably 2.3, but might have been a beta), but on the win7 PC no nomad had been installed before

I don't suppose you have dates for when these both were initially installed?

win10 (successful) nov 19
win7 (semi-successful) nov 4

Thanks for that. Just trying to narrow possibilities down.

If possible, could you go into device manager on both systems and see what driver date and version is being reported for each systems IO Card/Gadget?

the win7 machine belongs to i client and i no longer have access to it, sorry. but just to make sure that we're talking about the same thing: the problem in my case was not that the driver didn't work, the problem was that the installer didn't install the driver. after i pointed windows to the directory everything went smoothly...

the win7 machine belongs to i client and i no longer have access to it, sorry. but just to make sure that we're talking about the same thing: the problem in my case was not that the driver didn't work, the problem was that the installer didn't install the driver. after i pointed windows to the directory everything went smoothly...

That's OK, wishful thinking on my part :) Thank you for your information so far.

Yes, we are on the same page for sure. Based on driver version that's installed it would tell me some things about the installer it came from. Also, a driver can be rejected by windows from the installer but still be pointed to manually and work. It's not so much the driver as it could be things like a security certificate for instance causing windows to disallow the driver to be installed automatically, but windows will allow the driver to be used when manually installed.

If I have more questions I'll send a PM or something.