| Main > Main Forum |
| LEDBlinky and UltraStick mapping |
| << < (3/3) |
| arzoo:
--- Quote from: Petey09 on August 06, 2014, 11:28:17 pm ---Ok... I finally managed to make it worked has I was testing and it was a really stupid step missing. I had to run LedBlinky or Hyperspin as Administrator. Gotta love Windows. Now I feel stupid for not figuring this out earlier. Thanks alot arzoo for all your support. --- End quote --- No worries, glad you got it working. I'm going to add this info to the U360 section on the LEDBlinky support page. |
| IAmDotorg:
--- Quote from: Petey09 on August 06, 2014, 11:28:17 pm ---Ok... I finally managed to make it worked has I was testing and it was a really stupid step missing. I had to run LedBlinky or Hyperspin as Administrator. Gotta love Windows. Now I feel stupid for not figuring this out earlier. Thanks alot arzoo for all your support. --- End quote --- That's worth reporting to one, or both (I suspect LedBlinky, as running Hyperspin as Administrator is probably spawning a process that inheriting the administrator token from Hyperspin). In 2014, you should have very minimal situations where a process needs to be administrator. So something in that chain of execution isn't being done quite right and should be fixed. (Demand loading of a device driver wrong, or a manifest missing something if its loading a DLL to do it.) I haven't quite gotten to that point of configuration on my setup (the buttons aren't wired up, so I haven't touched LedBlinky yet other than installing the license). If I see the same problem, I'll fire up procmon/procexp, figure out what call is failing without admin rights and report it to the offending party. :) |
| Navigation |
| Message Index |
| Previous page |