Heads up to the Nomad community on an issue I ran into this weekend.
TLDR: Installing the latest Hog4PC release onto the same machine as my EOS Nomad resulted in Hog grabbing control of the driver for the Gadget. Besides uninstalling Hog also had to go into device manager and delete the driver for "Hog Widget" and then reinstall the EOS driver manually. After that sequence everything returned to normal in EOS Nomad.
I have been reliably using Nomad (2.9.1.17) on my Surface with a Gadget II for years, but this weekend suddenly it stopped wanting to recognize the Gadget and as a result was not outputting any DMX. 2 hours before a show was a really bad time for this to pop-up and I was at a loss as to what could be causing it.
To be clear I had not allowed any Windows Updates between the last gig and this one so it seemed unlikely to be a Windows driven issue. Uninstalling and reinstalling didn't do the trick either, and obviously reboots didn't help either. After pressing my backup into service (thank goodness for always having a backup machine available) I spent the rest of the weekend trying to sort out what happened.
To make a long story of OS updates, installing the Sentinal key update from Gemalto and uninstalling and reinstalling EOS multiple times I finally realized what the only real configuration change to the machine had been between the last working state and the now unresponsive Nomad installation. During the week I had chosen to update the Hog4 version on the machine to 3.13.1 (Build 2885) and in the process that seems to have hijacked the Gadget driver and made the Gadget invisible to EOS. Anytime I would plug the Gadget in, it would pop up in Device Manager as a High End Systems Hog Widget and was not recognized in EOS.
After uninstalling HOG and EOS and then reinstalling EOS, I found that the drivers in C:\Program Files (x86)\ETC\ETC_WinUSB_Drivers were not reinstalled but I had them from another machine so was able to copy them over. Strangely the device that initially showed up in Device Manager under Other Devices>I/O Interface BLK would not install the drivers using the standard Update driver function and searching for the directory noted above. I was able to force install the driver by going to the directory and right-clicking on the .inf file for the Gadget HighSpeed and selecting the Install option. Once the driver was installed, the Gadget was properly identified and EOS Nomad is back in business.
This support note from ETC (support.etcconnect.com/.../Manual_Installation_of_Gadget_Driver_on_Windows) really helped to point me in the driver direction and has the steps nicely laid out.
It seems odd that updating Hog4 caused this issue since they are both ETC products and I would assume there would at least be some regression testing to make sure that things like this didn't happen, but it is complicated software so things can slip through. I will also be posting this on the ETC forums.
Hope this helps somebody else that might be facing the same type of issue save a few hours and get back in business more quickly.
