Incorrect Rego in Alerts

[Mista Uzi]

Hi all
I know it is no longer supported, but having an issue with FD7 since, I think, upgrading to WIN10.
Program appears to run OK and is pointing to the correct SQB location.
I use the Flight Alert option to send an email on any interested aircraft in my location.
Therefore SBS Interested and Keep between sessions are ticked.  On loading shows about 6000 aircraft selected, which for my region is about right.

However
When it emails an alert it does one of two things.  Either emails just the hex code without any attached rego, or sends the interested hex code with a random registration.  Example a 7Cxxxx with G-EZGI. 

Any one any thoughts on this?

Thanks

MarkD

[Anmer]

Is FD using the correct BaseStation.sqb file?

[Mista Uzi]

Yes>double checked that

Still doesn't explain why it uses the correct hex code, generally 7Cxxxx which is VH- and a random rego

Just had one now

Flight  Detected (ID)
at 20:13:17
Flown by ET-AQP : B738
ModeS 7C7A49
Squawk

7C7A49 decodes as VH-YFV a Virgin Australia B738.  Showing on my SBS correctly.  Certainly not an Ethiopian B738 which would certainly be of interest in Australia

[Anmer]

Is anything else accessing the sqb file to read/write?

[Mista Uzi]

Now that is a different story.
Bear in mind this setup is no different to before i updated to WIN10

This is a dedicated PC and runs
SBS3 Basestation
Planeplotter
PBLink3
FD7
Virtual Radar
BADG

Probably all access at some point the SQB
Only other change I have made recently is installing a new app to feed to FR24

Perhaps a process of ellimination is in order.
Run SBS, then FD7 and take it from there

[Anmer]

I'm not suggesting there isn't an issue with FD7 but there have been no updates and it's just accessing the sqb file which hasn't been changed either.

Your approach looks a sensible one.

[Mista Uzi]

Just an update to this.


Ran BS then FD7 and all working as it should be.

Back up to all listed aps and have no further issues.

So
Buggered if I know

Thanks for suggestions

[Anmer]

Thanks for the update and letting us know it's all OK now.