Welcome to Radarspotting. Please login or sign up.

May 18, 2026, 03:57:23 AM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

FTD2xx.DLL

Started by KeithH, April 29, 2020, 01:12:45 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

KeithH

Whilst it's cloudy and we're locked down I thought I'd have play with the flightaware dongle I order a couple of weeks ago.  So dug out an old laptop to test the installation of the dongle, drivers and modesdeco.  I intended to use Basestation and the dongle when out and about.

The laptop (windows 10) immediately started a Windows update so I let it finish.  Basestation was last used on this machine about 10 weeks ago with no problems.  All OK then.

The installation of the drivers and modesdeco went ok and I could see data flowing, using the dongle.

Next was to start-up Basestation but the error message indicating FTD2xx.dll was displayed.  OK, so tried running CDM20814_setup. 

No joy.  Although the program appeared to run OK no .dll appeared to be installed in Windows\system32 or windows\system ??  So copied the file from my desktop (also Windows 10 and Basestation working well) into ..system32.

Still no joy and same missing error.  So copied file to ..\system.

Now error message is "The application was unable to start correctly....."

Tried uninstalling Basestation and re-installing (I use c:\kinetic\Basestation) but exactly the same.

Both machine are 64 bit.

Anyone come across this?

I'm out of ideas other than re-building windows on the laptop. 

I'm reluctant to try the same on the desktop if the same thing happens.

If you have read this far then many thanks.  Hope the above makes sense.

Anmer

Can I recap my understanding.

You've reinstalled BaseStation into your nominated folder, C:\Kinetic\BaseStation?

Is there an ftd2xx.dll file in this folder?

How are you launching BaseStation?  From a desktop shortcut?

And when you launch it, what excatly happens?  Do you get an error message at that point or does it launch and then generate an error message?

Can you post some screenshots of what you get?
Here to Help.

KeithH

Hi, thanks for the reply.

Yes, I've tried a re-install after copying the file manually with no change in the problem.

If I put the dll in the Basestation folder I get the "unable to start" message.

I've tried starting Basestation from the desktop shortcut and manually from the exe in c:\kinetic\basestation.  Same result each time.

When launching either of the messages are displayed immediately.  Basestation makes no attempt to start (Not flash screen).

Whilst typing I've a thought of downloading from internet a totally new file and manually copying.  But isn't that what CDM20814_setup does??

Thanks again.

[attachment deleted reduce file load]

KeithH

Anmer,

Just to let you know I have now got Basestation working.

Whilst replying to your message I had the idea of downloading a complete fresh .dll from the internet and it worked.

I'm still at a loss as to why copying the file from the desktop or running CDM20814_setup didn't work as I have done that in the past.

Oh well shouldn't loose sleep over it.

Pressing on with my tests now :o)

Thanks again for your help.
Regards
Keith

Anmer

Good to hear you have BaseStation working again.

It could have been a file permission issue.  The copied file may have been "blocked".  Right clicking the file would show Properties and a Security block may have been attributed. It can then be unblocked.

I've seen this in the past.

[attachment deleted reduce file load]
Here to Help.

KeithH

Quote from: Anmer on April 29, 2020, 03:07:28 PM
Good to hear you have BaseStation working again.

It could have been a file permission issue.  The copied file may have been "blocked".  Right clicking the file would show Properties and a Security block may have been attributed. It can then be unblocked.

I've seen this in the past.

mmm thanks.  First time I've seen that.  I'll store that in the back of my brain for future!:)

Just tested that - I hadn't deleted the old file yet from a temporary directory, and it doesn't show that warning.

I'm just re-applying the Microsoft update (forgot to say, I restored the system after the problem appeared) and will report back if the issue re-appears.

Many thanks

Keith