finally I found the time to install "Win10 Pro 64bit" on a clean computer. I always install on a clean computer and I never do any operating system updates. This is my favorite way since the early days of Win NT and WinXP and it is based on experience. This way I have never had any troubles with new operating system versions. Whenever I have used the update option in the past, I ran into troubles. So I believe in clean installs. It's just my experience.
After a successful installation of EFB 1.5.1 (downloaded from the AivlaSoft website) I started the DataProvider and the first what I got was the following screen from Win10 which is telling me that EFB requires the .NET framework 3.5:
Then I started the DataProvider and added a trial license. After that, I could select the options and the DataProvider started with the analysis of the FSX scenery data. No problems so far.
The DisplayUnit startet up without any problems too.
I guess that it is important to install Win10 on a clean computer and not to do an update from Win8.1 or any other operating system.
Well, I'm not so sure about that. I did in-place upgrades on my FSX box AND my laptop. I like to run the DU on the laptop so I can go in another room and still monitor a long flight The DU was working on the FSX build just fine after the upgrade. Then, after the first Windows Update the DU stopped working, and the fonts got all wonky in the DP settings. However, the laptop has undergone the SAME updates, but the DU works flawlessly.
What's interesting is that the FSX build is running AMD FX and the laptop is running Intel i5. I've also noticed that the fault (looking at the application event log) starts in KERNELBASE.DLL. The castle .net libraries make calls to this Windows API, so I have to wonder if the OS core components are architecture sensitive.
Cannot start Display Unit
in EFB v1 (Read only, no longer supported)
Posted
Well, I'm not so sure about that. I did in-place upgrades on my FSX box AND my laptop. I like to run the DU on the laptop so I can go in another room and still monitor a long flight
The DU was working on the FSX build just fine after the upgrade. Then, after the first Windows Update the DU stopped working, and the fonts got all wonky in the DP settings. However, the laptop has undergone the SAME updates, but the DU works flawlessly.
What's interesting is that the FSX build is running AMD FX and the laptop is running Intel i5. I've also noticed that the fault (looking at the application event log) starts in KERNELBASE.DLL. The castle .net libraries make calls to this Windows API, so I have to wonder if the OS core components are architecture sensitive.