Has anyone managed to get Basestation working under Windows 10 ?
Firstly it came up with the 'FTD2xx.dll not found' problem we have seen in the past, however after I downloaded the latest installer from the website, I now get a 'BaseStation.exe - Application Error - The application was unable to start correctly (0xc000007b). Click OK to close the application.
I will ask Kinetic about this, but wondered if anyone else had tried this.
Mike
http://www.tomshardware.co.uk/forum/53942-63-0xc000007b-error-windows
Hope this helps
How did you install BaseStation on your Windows 10 device?
I think this may have been an upgrade Mike. Windows 10 not been released on new pc's yet
You may be right, but I prefer to make sure.
Windows 10 is only available as a beta (Technical Preview if I recall). I don't know if it installs as an upgrade or overwrites any existing version.
I had already installed Win10 as a VM.
Just installed BS to C:\Kinetic\BaseStation and yes it does complain about FTD2XX.dll being missing.
Downloaded a version from here:
http://www.dll-files.com/dllindex/dll-files.shtml?ftd2xx [Choose Manual Fix to just download the zip file!]
Put ftd2xx.dll in BaseStation folder and it starts ok.
Quote from: IanH on January 28, 2015, 10:09:54 AM
Just installed BS to C:\Kinetic\BaseStation and yes it does complain about FTD2XX.dll being missing.
I had the same issue with Windows 7 on a new desktop here a few weeks back. Installing the file resolved the issue.
But I didn't get:
Quote
I now get a 'BaseStation.exe - Application Error
Thanks to all for their assistance, Ian's link to the .dll file fixed things, it worked after that.
Mike
Hi Gents,
After dealing with the initial "FTD2xx.dll not found' problem, I'm now having the same issue as Mike on the first post of this thread. I have just updated my PC from W7SP3 to W10 and am getting the dreaded 0xc000007b "The application was unable to start correctly" error message when trying to run Basestation.
Curiously, Basestation reporter runs perfectly!
I have tried pretty much everything:
1. Re-installed in a folder of my choice.
2. Re-installed in the Windows program files folder it tells you to.
3. Run as administrator ticked in properties.
4. Run as administrator from the desktop shortcut.
5. Tried to run in all the compatibility modes through properties.
6. W10 is fully updated.
7. Ran chkdsk, no issues.
8. Re-installed all the Visual C++ packages.
10. Prayed to any God who would listen!
My PC is a 64bit machine with a GFX295 card and Directx 12.
Anyone out there have any suggestions? Apart from go back to W7 which I cant do as I have a greater requiremnt to run W10 on this PC.
MTIA (again!)
Paul
BaseStation runs OK on Windows 10. I'm running it here.
Is yours a fresh install of BaseStation or are you copying any existing data files, such as the sqb, Ini, Waypoints, Outlines, OperatorFlags etc?
Quote from: Anmer on September 18, 2020, 09:07:57 PM
BaseStation runs OK on Windows 10. I'm running it here.
Same here, I've never had any issues. I know that doesn't help the OP, but it proves it's not a fundamental issue with the OS.
The .dll issue is common, but easily fixed.
At least it's good to know it should work on W10.
Both re-installs have been fresh installs, but I've kept all the old Basestation files and folders in a "Basestation Temporary" folder. I've not tried copying and pasting the old to the new yet.
Is it with removing all of it then trying again? Should the all the old files and folders have any effect?
Yes the .dll issue was easily dealt with.
Paul
I'd try a new install of BaseStation to a nominated folder, such as C:\Kinetic.
Download the version 184 CD and extract the files to a temp folder. Next run Setup and install to the new Kinetic folder. Do not attempt to use any existing files.
http://www.kinetic.co.uk/basestationdownloads1.php
Then launch BaseStation. I can't think of any reason, other than a missing .dll, why it shouldn't run OK.
If everything runs OK, you can then think about using backed up files.
Please report back on how you get on.
Tried that, still comes up with xc000007b "The application was unable to start correctly". Application error.
Some googling brings up a whole host of issues which as per my first post I have tried to correct, everything from using an earlier version of .net framework to re-installing the C++ packages.
Its very frustrating. I'll keep trying.
It worked perfectly with this machine on W7 and reporter works.
BaseStation doesn't use .Net.
At what stage do you get the error? Does the Setup complete OK?
How are you launching BaseStation?
Setup works fine as far as I can tell. All the appropriate folders end up in the correct place.
I have tried to launch BS from the shortcut and the .exe file in the BaseStation folder.
I have used "run as administrator" (RAA) and I have also tried not using RAA.
I still have all my old files and folder in a temporary folder. BS reporter works fine.
As soon as I double click the BS shortcut, whether RAA or not, the error code displays immediately, so the program doesnt get a chance to run.
Here is a screenshot of the error code.
[attachment deleted reduce file load]
Quote from: paulspot on September 19, 2020, 07:49:12 PM
Setup works fine as far as I can tell. All the appropriate folders end up in the correct place.
If you're running SetUp.exe from the extracted CD file, you should be able to observe the InstallShield Wizard and choose a folder for BaseStation. Did this complete OK?
The next step is to launch BaseStation and follow the BaseStation Startup Configuration. Here you set your location coordinates and how you are connceting to your SBS. This should culminate in Testing Your Setup. Did this complete OK?
Quote from: paulspot on September 19, 2020, 07:49:12 PM
BS reporter works fine.
Reporter is a database viewer and quite separate from the BaseStation application. I would ignore this for now. We need to get BaseStation running.
Have you tried all these recommendations:
https://windowsreport.com/0xc00007b-windows-8-1/
BaseStation is a 32bit app that will run on either 32 or 64 bit versions of Windows.
Do you have just the one hard drive in your PC? Have you checked it for errors?
The bottom line is BaseStation runs OK on Windows 10. But your system has a localised issue.
"If you're running SetUp.exe from the extracted CD file, you should be able to observe the InstallShield Wizard and choose a folder for BaseStation. Did this complete OK?"
Yes, I have tried to re-install countless times now and each time this works ok.
"he next step is to launch BaseStation and follow the BaseStation Startup Configuration. Here you set your location coordinates and how you are connceting to your SBS. This should culminate in Testing Your Setup. Did this complete OK?"
No, as I stated, whe you double click to run the program, the only thing that happens is the error message appears.
"Do you have just the one hard drive in your PC? Have you checked it for errors?"
I only have one HD and yes, I have run chkdsk, the HD does not have any errors.
Quote from: paulspot on September 19, 2020, 08:22:53 PM
No, as I stated, whe you double click to run the program, the only thing that happens is the error message appears.[/b][/color]
Sorry to sound pedantic, but do you get the error message when you select Finish at the end of the BaseStation Startup Configuration?
[attachment deleted reduce file load]
Just PM'd you Anmer.
OK are there step by step instructions to installing please?
Do you run the setup.exe directly from the zip folder?
"Sorry to sound pedantic, but do you get the error message when you select Finish at the end of the BaseStation Startup Configuration?"
The installation finishes.
I cant get to the start up configuration as when I double click on BS, I only get the error message.
Quote from: paulspot on September 19, 2020, 08:47:45 PM
Do you run the setup.exe directly from the zip folder?
No. You must exctract the files as I suggested a few posts back.
I'm now signing off for the evening. We can pick this up again tomorrow if you still have a problem.
I downloaded the zip file from kinetic, and unzip it on my desktop, first i created a folder in c:\Kinetic and inside this directory a folder Basestation. Then run the setup (right click and run as administrator) and install it in the c:\Kinetic\Basestation.
From then it must run fine.
You must unzip the downloaded file, not run in from inside winzip/winrar!!!!
Thanks Pipo. We've so far established it's not a reinstall error. It's a common'ish W10 error relating to App compatibility. I've been through virtually all the fixes, some a number of times, without any luck. Reinstalled.net framework and the C++ packages, run chkdsk reinstalled about 20 times varying different ways, run in all the available compatibility modes yet nothing works.
It's very very annoying as it's the only thing that doesn't work after the upgrade from W7.
Going to try and run it from a flash drive later which will rule out a number of other things.
Paul
Quote from: paulspot on September 20, 2020, 10:21:10 AM
It's a common'ish W10 error relating to App compatibility.
That may be true but I've rarely seen this attributed to BaseStation.
I had no issues upgrading from Win 7 to Win 10 (forced by Microsoft withdrawing support) and I know many others who are running BaseStation on Windows 10.
Please let us know ho you progress.
Im using Windows Pro 64bit on insiders program, and i also upgraded from Win 7 Pro to Win 10 Pro with the Microsoft free upgrade tool, and i did on a tip from Anmer to install Basestation in a own directory on c: "c:\Kinetic\Basestation" this due to the virtual folder and the sqb file.
Since then no problems on windows 10. Maybe there went something wrong on the upgrade Win7 -> Win10...
W10 upgrade went perfectly, lots of other Apps and Office etc all working perfectly. Literally the only one that doesn't is BS.
If you google the error code and research it, it's quite common after the upgrade for some people with some Apps or programs. It seems to be a C++ or graphics based issue.
I don't believe it's a BS issue so it wouldn't matter if you installed it up your sleeve, it still wouldn't work on my PC. It think it's more a confliction with something else on my PC.
In my previous posts you'll see the lengths I have gone to so far, including many many re-installs in every combination you could imagine. I've got 2 avenues to explore after the kids are in bed later.
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
Quote from: Oblivian on September 23, 2020, 09:04:24 AM
It's normally a .DLL mismatch
That issue was taken care of:
https://radarspotting.com/forum/index.php/topic,4893.msg49252.html#msg49252
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.
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]
Oh my word!!!!
Oblivian is absolutely 100% correct, well done that man. ;D ;D ;D ;D :P :P :P
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!!
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?
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.
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.
Thanks.
Strange, mine is 2.8.14.1 dated 01/01/2015. A much earlier version.
In which folder did you place it?
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.