Basestation - Windows 10

[Oblivian]

It's normally a .DLL mismatch

Likely the ftd2xx.dll included in the root to open the COM port to talk to the device. It won't be WHQL certified for 10

Assuming you are on x64. Over-write with the W10 supported version in the destination folder

https://www.ftdichip.com/Drivers/CDM/CDM%20v2.12.28%20WHQL%20Certified.zip

[Anmer]

It's normally a .DLL mismatch

That issue was taken care of:

https://radarspotting.com/forum/index.php/topic,4893.msg49252.html#msg49252

[Oblivian]

He said he's dealt with it not being found - but doesn't specify the version put in place to fix that error?.

Unless the missing one is replaced with a later signed/certified, it'll be similar as not being present. But likely won't execute and throw a windows error instead.

IE -  SBS Resources bundled 'dllfile' in SBS-resources 6.7 18.04.11 I still have stashed away (most people keep the 'working stuff' and often don't change unless really have to right?) = ver 3.1.6.1 - no W10 certification or 'Digital Signatures' tab under file info.

This, and most files in Basestation folder dated around the ~2010 mark

While the certified running version, is 3.2.14.0 (FTDI CDM driver files dated 2017) and seems to load. I expect others may be in a similar boat and running later ones?

I similarly had 3 large part shelve machines all stop working after a windows 10 update about July because the FDTI drivers were suddenly blocked.

But hard to tell without verifying the file version Paul has used. So suggested try the latest if not already.

[Anmer]

My ftd2xx.dll is dated 01/01/2015.  The same one I was using with Windows 7 and unchanged when I upgraded to Windows 10.

Attached here if it's of any use.

[attachment deleted reduce file load]

[paulspot]

Oh my word!!!!

Oblivian is absolutely 100% correct, well done that man.   

The ftd2xx.dll was an old version not WHQL certified and therefore W10 blocked it and showed the error message.

As soon as I replaced the newer version in the correct folder, hey presto! Bloody W10, cost me a few hours of my life.

A massive thank you to Anmer and Oblivion for resolving what I thought was a terminal error. Virtually the only thing I hadn't thought of was checking the date of the .dll file.

Happy days!!

[Anmer]

Great and a BIG thanks to Oblivian.

Out of curioisity what's the date of the "working" dll?  And the one that didn't work?

[G4UMW]

The most recent version of the ftd2xx.dll is v2.12.28.1 which was issued on 30th August 2017 (data from FTDI website). I can confirm that BaseStation works well with this version on Windows 10 Pro 64-bit.

[paulspot]

The working .dll Oblivion gave to me is: 2.12.28.1 19 Sep 17.

The one that didnt work is: 2.12.16.1 16 Mar 16.

[Anmer]

Thanks.

Strange, mine is 2.8.14.1 dated 01/01/2015.  A much earlier version.

In which folder did you place it?

[paulspot]

I placed Oblivions new .dll both in the System32 folder to replace the one there and in the BS folder to replace the one there.