Welcome to Radarspotting. Please login or sign up.

May 17, 2024, 05:57:34 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.

FD Error

Started by charliebrown, June 10, 2012, 10:14:18 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

charliebrown

I have started getting a problem with FlightDisplay_7_9_64_0

It has stated giving the error message attached below.

Running SBS1-er, PP, FD and Active Display Lite on Windows 7 64 bit version.

Any suggestions how to put this right.

regards

Charlie

[Attachment deleted by Admin to save file space]

Anmer

Hi Charlie

Do you get the message if you just run FD and not with AD at the same time?  And does the message occur randomly or always when you do something?
Here to Help.

charliebrown

#2
Hi Mike

Only started happening this morning.

I start up Basestation then FD and this message then pops up even before I press the FD start button every time without Active Display or PP running. 

If I then press the start button in FD, I get a series of these error messages every time and Windows 7 says the FD programme has stopped working wants to send the error to MS.

I would normally Start BaseStation, FD, PP then Active Display Lite in that order.

Regards


Charlie

Anmer

Open Task Manager and see if any FD process are running in the Processes tab.

If they are, End them.  Then restart FD.  If you still get the error I'll ask Allan Bird for his advice.
Here to Help.

charliebrown

Hi Mike

Tried what you suggested and still getting the errors.

Just noticed, I get message attached very briefly after pressing the FD start button before all the duplicated errors appear.

Regards,


Charlie

[Attachment deleted by Admin to save file space]

Anmer

Thanks Charlie, I'll get in touch with Allan Bird and get back ASAP.
Here to Help.

charliebrown

Hi Mike

I thought I might try a reinstall of FD and this seems to have cured the problem.

Not sure what caused it in the first place.

Regards


Charlie