Windows 11 & Basestation

[Paul1]

Hi Mike

No problem will speak to you this afternoon

[Anmer]

I've just spent an hour remotely connected to Paul1.

Then, towards the end of the session, no one appeared to be available so I had to disconnect.

I'll summarise what I found.

Basestation and ADU were running.  Some logos were displaying but not all.  Those that were missing were in the OperatorFlags folder with a matching code in the aircraft record.

On closing Basestation it automatically restarted which I assume was a batch file.  Closing ADU stopped the restart.

Paul explained he normally starts Basestation from a desktop shortcut.  On looking at the shortcut Properties, the target was in ProgramFiles (X86) whereas the previous posts implied it was in a nominated folder outside of ProgramFiles.  Such a folder existed.

On checking the OperatorFlags folder, with over 15,000 files, there were some odd sized files.

I zipped all the files and transferred them to my PC and ran BmpChk, results as follows:

BmpChk V2.0

Checking bmp files in I:/LCN Websites/Radarspotting/logos2
Dimension 83 x 20 for file 181AS.bmp is unusual
Dimension 94 x 22 for file 412FLTSC20.bmp is unusual
File length mismatch 5174 6144 for file 522SOS.bmp
Dimension 86 x 20 for file 652SQNAACWildcat.bmp is unusual
File length mismatch 5174 6144 for file 660SQNAAC_4.bmp
File length mismatch 5174 6144 for file 668SQNAAC_8.bmp
File length mismatch 5174 6144 for file 670SQNAAC_9.bmp
File length mismatch 5174 6144 for file 76ASC20H_105.bmp
Dimension 74 x 26 for file AA, AX.bmp is unusual
Dimension 85 x 21 for file Ambeo_35.bmp is unusual
Dimension 85 x 24 for file AS65black_8.bmp is unusual
Dimension 85 x 24 for file AS65blue_9.bmp is unusual
Dimension 90 x 20 for file BTTC680.bmp is unusual
Dimension 85 x 18 for file CARTIER.bmp is unusual
Dimension 60 x 20 for file CJM.bmp is unusual
Dimension 85 x 21 for file COKEGALX_28.bmp is unusual
Dimension 85 x 22 for file D11.bmp is unusual
Dimension 90 x 20 for file DA62_1.bmp is unusual
Dimension 85 x 18 for file DBR.bmp is unusual
File length mismatch 5174 6144 for file DNU_2.bmp
Dimension 85 x 18 for file EBA.bmp is unusual
Dimension 85 x 18 for file EEX.bmp is unusual
Dimension 85 x 18 for file EFP.bmp is unusual
Dimension 85 x 18 for file EHY.bmp is unusual
Dimension 84 x 25 for file Enable_10.bmp is unusual
File length mismatch 5174 6144 for file ESWGLF4_88.bmp
Dimension 85 x 18 for file ETR.bmp is unusual
Dimension 85 x 18 for file FCN.bmp is unusual
Dimension 85 x 18 for file FKG.bmp is unusual
Dimension 84 x 20 for file FKS.bmp is unusual
Dimension 90 x 21 for file Flairjets_1.bmp is unusual
Dimension 85 x 22 for file G-EMAA.bmp is unusual
File length mismatch 5174 6144 for file G-LENM_1.bmp
File length mismatch 5174 6144 for file G-LENM_4.bmp
Dimension 84 x 25 for file G-OCON_20.bmp is unusual
Dimension 93 x 21 for file GJS.bmp is unusual
Dimension 85 x 21 for file HeliairR22_1.bmp is unusual
Dimension 85 x 18 for file HIA.bmp is unusual
File header "‰P" (0x89 0x50) should be "BM" in file Hop.bmp
File length mismatch 168642382 1895 for file Hop.bmp
Dimension 21760 x 0 for file Hop.bmp is unusual
Dimension 85 x 18 for file HST.bmp is unusual
Dimension 87 x 20 for file HSV.bmp is unusual
Dimension 85 x 22 for file IAC.bmp is unusual
Dimension 85 x 22 for file IACFTS.bmp is unusual
File length mismatch 5174 6144 for file IAMKC767.bmp
Dimension 85 x 18 for file IL62.bmp is unusual
Dimension 85 x 18 for file JGA.bmp is unusual
Dimension 84 x 25 for file Kuki Heli R44_12.bmp is unusual
Dimension 85 x 18 for file KVA.bmp is unusual
File length mismatch 5174 6144 for file LUCC510_34.bmp
Dimension 90 x 21 for file LWGE50P_15.bmp is unusual
Dimension 90 x 21 for file LWGE50P_3.bmp is unusual
Dimension 85 x 18 for file LXP.bmp is unusual
Dimension 85 x 18 for file MCS.bmp is unusual
File length mismatch 6198 7168 for file MFTAS65_1.bmp
Dimension 85 x 24 for file MFTAS65_1.bmp is unusual
File length mismatch 5174 6144 for file MFTBE76_3.bmp
File length mismatch 5174 6144 for file MFTG-CGMF_27.bmp
File length mismatch 5174 6144 for file N100JZ_65.bmp
File length mismatch 5174 6144 for file NJEGLEX_109.bmp
File length mismatch 5174 6144 for file OE-GUN_28.bmp
Dimension 85 x 21 for file PDYGALX_17.bmp is unusual
File length mismatch 5174 6144 for file PEAF-HIPE_18.bmp
Dimension 85 x 22 for file POLICE.bmp is unusual
File length mismatch 5174 6144 for file PEAF-HIPE_18.bmp
Dimension 84 x 25 for file R44_3.bmp is unusual
Dimension 60 x 20 for file RFA.bmp is unusual
File length mismatch 5174 6144 for file RFLC525_63.bmp
Dimension 85 x 18 for file ROK.bmp is unusual
File length mismatch 5174 6144 for file RSAF24SQN_3.bmp
File length mismatch 5174 6144 for file RSAFMRTT_2.bmp
Dimension 85 x 18 for file SOC.bmp is unusual
Dimension 89 x 20 for file SwedAFS102B_91.bmp is unusual
Dimension 84 x 25 for file SXNG-KLNJ_18.bmp is unusual
Dimension 85 x 18 for file TAV.bmp is unusual
Dimension 86 x 20 for file TC-GAP.bmp is unusual
Dimension 86 x 20 for file TC-GAP_101.bmp is unusual
File length mismatch 5174 6144 for file TOM788_11.bmp
Dimension 77 x 20 for file Trout99.bmp is unusual
Dimension 800 x 248 for file trustair-logo.bmp is unusual
Dimension 86 x 20 for file TUAF212FiloGLF4_102.bmp is unusual
Dimension 93 x 21 for file UA, RP.bmp is unusual
File length mismatch 5174 6144 for file UAFMRTT_4.bmp
Dimension 85 x 18 for file VC10.bmp is unusual
File length mismatch 5174 6144 for file VFIC525_114.bmp
File length mismatch 5414 6144 for file VOEB717.bmp
Dimension 89 x 20 for file VOEB717.bmp is unusual
Test complete, 15564 files checked, 28 errors and 60 warnings

I deleted all the files with "File length mismatch" in the OperatorFlags folder in the ProgramFiles location.

When I went to restart Basestation from the desktop shortcut I got numerous error messages which suggested a corrupt setup.  It also suggested that Basestation had been running from a different location.

I asked Paul to restart ADU but received no reply.

I had no option but to disconnect the Remote session.

In my opinion, the operator logos/silhouette issue was caused by the rogue files in the OperatorFlag folder.  But I can't confirm this due to the Basestation launch errors and not knowing which Basestation.exe was being used when I first connected.  If it was the one in the discrete location, the cleaned up OperatorFlags folder needs to be copied to that directory.

As a footnote, I'm more than happy to undertake remote sessions but I do ask that the member remains available throughout.  Otherwise I can't get answers to questions and I'm uncomfortable being on someone else's PC without supervision.  This has happened a few times recently.