Appkey problem in logfile

[alexvs]

Pete,

I looked into my logfile (FS9, FSUIPC program version 3.71) and saw an "empty" appkey like this AppKey="9G9LCNT2MDUY".

I have running, FS9.1, ASV6 build 536, a posky 737-800 with the Skydecks version 3.15 panel.

Below a short lay-out of my FSUIPC logfile and the "empty" appkey is added again and again. Is this a problem and do you know where it's coming from? Do I have to fix something and do you also know how?

===================

Logfile

===================

********* FSUIPC, Version 3.71 by Pete Dowson *********

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Jeroen van Schoneveld"

User Addr="ja.vanschoneveld@quicknet.nl"

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=4000B7A7[4000B7A7]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

33594 System time = 19:20:21

33594 D:\Program Files\Microsoft Games\Flight Simulator 9\

33594 System time = 19:20:21, FS2004 time = 12:00:00 (00:00Z)

79985 D:\Documents and Settings\Jeroen\Mijn documenten\Flight Simulator Files\Alexvs1.flt

80235 AIRCRAFT\Opensky B737-800\OSBoeing737-800w.air

80360 Aircraft="POSKY Transavia Boeing 737-800 PH-HZQ"

81110 AppKey="PG4JGV6GUNBI", Module="atn.gau"

82157 AppKey="PG4JGV6GUNBI", Module="atn.gau"

82157 AppKey="PG4JGV6GUNBI", Module="atn.gau"

148485 AppKey="9G9LCNT2MDUY"

148594 AppKey="5G3EUHFOBQE4", Module="ActiveRadar.dll"

149141 Advanced Weather Interface Enabled

151516 AppKey="9G9LCNT2MDUY"

152219 NWI weather clear actioned

152219 External weather discarded

158485 D:\Documents and Settings\Jeroen\Mijn documenten\Flight Simulator Files\UI generated flight.flt

158969 AppKey="PG4JGV6GUNBI", Module="atn.gau"

159828 AppKey="PG4JGV6GUNBI", Module="atn.gau"

159828 AppKey="PG4JGV6GUNBI", Module="atn.gau"

160625 Clear All Weather requested: external weather discarded

230188 AppKey="9G9LCNT2MDUY"

237500 AppKey="9G9LCNT2MDUY"

243500 AppKey="9G9LCNT2MDUY"

248875 AppKey="9G9LCNT2MDUY"

254032 AppKey="9G9LCNT2MDUY"

259391 AppKey="9G9LCNT2MDUY"

265172 AppKey="9G9LCNT2MDUY"

270688 AppKey="9G9LCNT2MDUY"

276344 AppKey="9G9LCNT2MDUY"

281625 AppKey="9G9LCNT2MDUY"

288000 Traffic File #40 = "scenery\world\scenery\traffic_mrai_airberlin_su06"

288032 Traffic File #20 = "scenery\world\scenery\traffic_mrai_aerlingus_wi06-07"

288141 AppKey="9G9LCNT2MDUY"

289641 Traffic File #15 = "scenery\world\scenery\traffic030528"

289797 Traffic File #262 = "scenery\world\scenery\traffic_mrai_lufthansa_wi05"

290016 Traffic File #47 = "scenery\world\scenery\traffic_mrai_airdolomiti_wi06-07"

290203 Traffic File #123 = "scenery\world\scenery\traffic_mrai_britanniaairways_su05"

290360 Traffic File #51 = "scenery\world\scenery\traffic_mrai_airfrance_wi05"

290375 Traffic File #109 = "scenery\world\scenery\traffic_mrai_belair_su05"

290828 Traffic File #65 = "scenery\world\scenery\traffic_mrai_airone_wi06-07"

290844 Traffic File #104 = "scenery\world\scenery\traffic_mrai_austrian_su06"

290985 Traffic File #220 = "scenery\world\scenery\traffic_mrai_iberia_su06"

291141 Traffic File #74 = "scenery\world\scenery\traffic_mrai_airslovakia_su05"

291297 Traffic File #78 = "scenery\world\scenery\traffic_mrai_airvallee_wi06-07"

291313 Traffic File #117 = "scenery\world\scenery\traffic_mrai_bluepanorama_wi05"

291453 Traffic File #317 = "scenery\world\scenery\traffic_mrai_skyeuropeairlines_wi06-07"

291766 Traffic File #304 = "scenery\world\scenery\traffic_mrai_ryanair_wi06-07"

291782 Traffic File #379 = "scenery\world\scenery\traffic_pai_ga"

291922 Traffic File #255 = "scenery\world\scenery\traffic_mrai_livingston_wi05"

292078 Traffic File #118 = "scenery\world\scenery\traffic_mrai_bluepanorama_wi06-07"

292188 Traffic File #160 = "scenery\world\scenery\traffic_mrai_dhlairways_su05"

292500 Traffic File #180 = "scenery\world\scenery\traffic_mrai_eurofly_su06"

292532 Traffic File #331 = "scenery\world\scenery\traffic_mrai_sund-or_su05"

292594 Traffic File #377 = "scenery\world\scenery\traffic_pai"

292657 Traffic File #351 = "scenery\world\scenery\traffic_mrai_transavia_su06"

292703 Traffic File #89 = "scenery\world\scenery\traffic_mrai_alpieagles_wi06-07"

292766 Traffic File #161 = "scenery\world\scenery\traffic_mrai_dhleurope_wi05"

292797 Traffic File #124 = "scenery\world\scenery\traffic_mrai_britishairways_s06"

292828 Traffic File #277 = "scenery\world\scenery\traffic_mrai_myair_su06"

292907 Traffic File #143 = "scenery\world\scenery\traffic_mrai_clubair_su06"

292907 Traffic File #383 = "scenery\world\scenery\traffic_woa_alitalia_su06"

292938 Traffic File #279 = "scenery\world\scenery\traffic_mrai_neos_su05"

293625 Traffic File #272 = "scenery\world\scenery\traffic_mrai_meridiana_wi06-07"

293735 Traffic File #365 = "scenery\world\scenery\traffic_mrai_virgin_ex_su06"

293766 Traffic File #374 = "scenery\world\scenery\traffic_mrai_windjet_wi06-07"

367188 AppKey="9G9LCNT2MDUY"

373282 AppKey="9G9LCNT2MDUY"

379485 AppKey="9G9LCNT2MDUY"

385625 AppKey="9G9LCNT2MDUY"

391828 AppKey="9G9LCNT2MDUY"

397985 AppKey="9G9LCNT2MDUY"

404047 AppKey="9G9LCNT2MDUY"

410828 AppKey="9G9LCNT2MDUY"

417032 AppKey="9G9LCNT2MDUY"

423157 AppKey="9G9LCNT2MDUY"

429282 AppKey="9G9LCNT2MDUY"

435469 AppKey="9G9LCNT2MDUY"

441125 AppKey="9G9LCNT2MDUY"

[Pete Dowson]

I looked into my logfile (FS9, FSUIPC program version 3.71) and saw an "empty" appkey like this AppKey="9G9LCNT2MDUY".

What do you mean by "empty"? FSUIPC is just logging the fact that some program wrote that key to offset 8001. Since FSUIPC doesn't check these now, it doesn't go to all the bother to find out what the program is, but I left the logging of the Key as possibly useful information. Why does it worry you?

Below a short lay-out of my FSUIPC logfile and the "empty" appkey is added again and again. Is this a problem and do you know where it's coming from? Do I have to fix something and do you also know how?

It's certainly a little odd for a program to continually write its key to 8001 (in this case every, what, 6 seconds or so), and I don't know why it is doing that. Even the "ATN.GAU" does it three times in quick succession. But this isn't new in this version of FSUIPC.

The key "9G9LCNT2MDUY" is allocated to ASv6,"ActiveSky 6" by "HiFi Simulation Software", if you want to contact them about it.

Regards

Pete

[JSkorna]

Hi,

Do a uninstall reinstall cycle of AS and see if this goes away.

[alexvs]

Pete and Jim,

Thanx for the quick answers. I did a clean re-install (first de-installed everything) with ASV6 build 533. The problem still exists. What can I do now?

[Pete Dowson]

Thanx for the quick answers. I did a clean re-install (first de-installed everything) with ASV6 build 533. The problem still exists. What can I do now?

What is the actual problem? What doesn't work? Why are you looking at the log?

Pete

[alexvs]

Pete,

Nothing wrong actually. Yesterday I had a CTD (d3d9.dll) and I allways look at some logfiles. Not that I think this issue has to do something with this CTD, but I think it's weird that a program is logging an entry so many times in your logfile, when I think this has never been the case before. Don't you think so also? I'm an informationanalist at Getronics (International ICT company) and everything that's overdone in logfiles bother me :) .

[Pete Dowson]

I think it's weird that a program is logging an entry so many times in your logfile, when I think this has never been the case before. Don't you think so also?

I think it is odd that it is writing its Key every few seconds, yes, but if it is working okay it isn't really a problem. Although your log will grow slowly, it is started again on each FS session so it shouldn't present a disk space problem.

Whether this is new behaviour or not I couldn't say. I'd need to delve into my archives to find earlier FSUIPC code to see whether I would have logged every instance in earlier versions. I really don't have time right now.

Regards

Pete

[alexvs]

Pete,

I just discoverd that the " A320.gau" from Eric Marciano is also writing a lot of entries in the logfile. So in combination with ASV6 and the panel of Eric the logfile is growing very rapidly. I'll see if with an earlier version the writing in the log is stopped. I will contact you here when I know the version.

[Pete Dowson]

So in combination with ASV6 and the panel of Eric the logfile is growing very rapidly.

"Very rapidly"? I don't know about the A32o gauge, but for ASV6, at around 25 bytes each 6 seconds, even in a 12 hour flight it will grow by less than 180kb. Are you really seriously that short of disk space?

I am finding it very hard to get excited by all this I must admit.

Regards

Pete

[alexvs]

Pete,

Enough harddrive space. I did some tests:

In the versions 3.65 and 3.70 the logging of ASV6 and A320.gau is not so large. Also I noticed that after a module or gauge is logged it now says in version 3.70 "Module [M4] identified = "ATN.GAU" Module [M4] "atn.gau" access registration is okay". In the log of version 3.71 this is not the case. The multiple logging of ASV6 is also hapening in version 4.xx (FSX version).

I am finding it very hard to get excited by all this I must admit.

That's okay Pete. You are busy I think. I thought you would have liked to know this "incident". Maybe I struk on a problem :? .

[Pete Dowson]

In the versions 3.65 and 3.70 the logging of ASV6 and A320.gau is not so large.

You mean "not repeating", I assume? This will simply be because FSUIPC keeps a list of the last few programs which registered with it so it doesn't need to check them again. Since I removed the checking it doesn't know the program name and doesn't need to keep a list because it isn't re-checking each time. Despite the extra lines in the Log, I assure you the new method is faster!

Also I noticed that after a module or gauge is logged it now says in version 3.70 "Module [M4] identified = "ATN.GAU" Module [M4] "atn.gau" access registration is okay". In the log of version 3.71 this is not the case.

Of course not. as I told you, there is no access registration checking now. The logging of the key is only for information.

I thought you would have liked to know this "incident". Maybe I struk on a problem :? .

Oh dear. Please do refer to the very first answer I gave in this rather extraordinary thread. I said:

FSUIPC is just logging the fact that some program wrote that key to offset 8001. Since FSUIPC doesn't check these now, it doesn't go to all the bother to find out what the program is, but I left the logging of the Key as possibly useful information. Why does it worry you?

If there is any "problem" it is only that I am puzzled as to why you think it is a problem in the first place, even warranting spending all this time on investigating things I know about and which are designed that way.

If you are seriously just objecting to having multiple lines in the Log, then I'll make a note to make them optional in future, possibly only logging them if "Extras" are requested in the Logging. But it is in no way a priority item, and it most certainly isn't a "problem" as far as I can see.

Otherwise, if you are just trying to be helpful, then, thank you very much, but there was no need and I thought I'd answered it all in the first reply. ;-)

Regards

Pete

[alexvs]

Pete,

Indeed, I was trying to be helpful :) . Thanx for the answers.