Windows 10: phidget21.dll not loaded on Win10 Pro but work fine on Win7,8,10 home

I'm helping a small museum, who had a PC running Win 7- 64 bit, a 3.party have written a program in Unity about 4 years ago. We can't get hold in anyone from the 3.party The PC have 2 USB Phidgets interfaces a GPIO for trigger the software and a analog 0-10V output to control some external equipment, all worked fine on the Win7 PC The harddrive died and IT have installed a new harddrive with Win10 PRO since 7 is not supported anymore so a company policy. A folder with the 3.party software have been reinstalled and the Phidget driver has been installed.. v21 since v22 does not talk with the 3.party program. (I have tested with success on win 7,8, and 10 home) OS - Windows - Phidgets Legacy Support Unity Real-Time Development Platform | 3D, 2D VR & AR Engine If we open the Phidget control panels we can see the USB interfaces and read input and set output so that part works fine On the Win10 Pro there is generated a logfile from the 3.party soft and it does contain this Fallback handler could not load library E:/Exp/Windtunnel/10_01_2017/winds_Data/Mono/phidget21.dll Fallback handler could not load library E:/Exp/Windtunnel/10_01_2017/winds_Data/Mono/.\phidget21.dll Fallback handler could not load library E:/Exp/Windtunnel/10_01_2017/winds_Data/Mono/phidget21.dll etc This is even if we place a copy of the phidget21.dll in the same folder as the exe file. The user on Win10 Pro has been made a Admin The defender/firewall has been disabled I have communicated with Phidgets and the have not ideas. I have communicated with Unity , and the say find the 3.party...not possible or contact Microsoft ...not easy I need a good ides to why this happens on Win10 pro ... gues for sure it's so right issue

:)

 

Win7 Pro (OEM) to Win10

Thanks Andre.

Just as I knew...

My original question was why I wasn't able to chose Win10 Pro when using the MCT from within Win7 Pro OEM. I'm guessing my original suggestions were correct?

Henry

 

Windows 10 Pro or Windows 8 Pro from Windows 7 Pro ?


Just replaced motherboard on my old Dell D830 that I had upgraded to Windows 10 Pro from Windows 7 Pro last August.

Went through steps on setting up new MOBO and it is up/working just fine.

I happened to run Belarc Advisor just to get a snapshot of data for the file. What is interesting is that Belarc indicates the O/S is Windows 8 Pro (build 9200).

I looked at another recent thread here at TenForums and also took some of the steps suggested and figured that maybe I needed to install or re-install Windows 10. I checked the Update/Security/Activation tab and it indicates that Windows 10 Pro is installed, activated with a digital entitlement.

So ... why does Belarc seem to see only Windows 8 Pro? Maybe because of the "maturity" of the D830? I know that Dell has disclaimers at their site that says the D830 has not been certified for Windows 10.

So, it is working, but the data from Belarc just has me scratching my head.

Any suggestions or thoughts?

 

Win7 Pro (OEM) to Win10

Just tried to use the MS 'Media Creation Tool' to download an .iso of Win10 Pro 64-bit - the only OS offered in the dropdown box is Win10 Home!

Currently running Win7 Pro (OEM) on my last machine to be upgraded. I haven't yet done the automatic 'upgrade' to Win10. Of course, I know I need to do this before doing a clean install with a downloaded .iso. Is this the reason for no choice of the Pro
version?

If first I do the free upgrade from Win7 Pro (OEM) to Win10...

a) Will the upgraded OS show as Win10 Pro (OEM)?
and;

b) If I then run the 'Media Creation Tool', will I then be offered a choice of Win10 Home or Win10 Pro in the drop-down?

It was always my understanding that Win7 Pro (OEM) was entitled to a free upgrade to Win10 Pro (OEM)...

Am I missing something?

Thanks,

Henry