FS Flight Tracker

[Trevor Brooke]

Hey guys, I have a question about the FS Flight Tracker application. This is mainly aimed at Pete, but if any of you have any info, please don't hesitate to post. So, I recently got FS Flight Tracker and when I run it (push the "On" button) it gives me the "not accredited for access to an unregistered copy of FSUIPC". I've e-mailed someone from Cathay Pacific Virtual (they require FS Flight Tracker to be used), but have not received a response. I have registered on their forums, but not been accepted in two days. I was wondering if there was an application key (can't find one in the list), or if I'm just doing something wrong. On the download page for FS Flight Tracker, it says that the program uses FSUIPC with Pete's permission. What am I doing wrong?

[Pete Dowson]

So, I recently got FS Flight Tracker and when I run it (push the "On" button) it gives me the "not accredited for access to an unregistered copy of FSUIPC"

...

I was wondering if there was an application key (can't find one in the list), or if I'm just doing something wrong. On the download page for FS Flight Tracker, it says that the program uses FSUIPC with Pete's permission.

FlightTracker was granted an FSUIPC access code in July 2003. As far as I know it uses this to gain automatic access to FSUIPC, with no special action needed by you. Please let me see the FSUIPC log file.

Regards,

Pete

[Trevor Brooke]

Here it is:

********* FSUIPC, Version 3.41 by Pete Dowson *********

Running inside FS2004(original release)

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Module base=61000000

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

WeatherOptions(Orig)=0000B027[0000B027]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=0

40078 System time = 17:37:53

40118 \\TREVORBR\Program Files\Microsoft Games\Flight Simulator 9\

40128 System time = 17:37:53, FS2004 time = 12:00:00 (00:00Z)

50843 FLIGHTS\OTHER\FLTSIM.flt

51013 AIRCRAFT\c172\Cessna172SP.air

52435 Aircraft="Cessna Skyhawk 172SP"

97420 C:\Documents and Settings\Trevor\My Documents\Flight Simulator Files\Cathay Pacific.flt

97871 AIRCRAFT\A340-600\A340-600.air

99403 Aircraft="Airbus A340-600 Cathay Pacific"

107234 Clear All Weather requested: external weather discarded

123337 Advanced Weather Interface Enabled

159850 Client Application: "FlightTracker" (Id=1684)

159850 D:\Program Files\FS FlightTracker\FlightTracker.exe

159980 Product="FS Flight Tracker"

159980 Company="K. D. Lovell"

160220 Illegal read attempt: offset 023E, size 2

160220Program or module not accredited for use with this unregistered FSUIPC

161512 ### IPC Message processed in 1302mSecs ###

611209 ### IPC Message processed in 1242mSecs ###

686627 System time = 17:48:40, FS2004 time = 23:33:28 (16:33Z)

686627 *** FSUIPC log file being closed

Memory managed: 4702 Allocs, 5206 Freed

********* FSUIPC Log file closed ****

[Pete Dowson]

159850 Client Application: "FlightTracker" (Id=1684)

159850 D:\Program Files\FS FlightTracker\FlightTracker.exe

159980 Product="FS Flight Tracker"

159980 Company="K. D. Lovell"

160220 Illegal read attempt: offset 023E, size 2

160220Program or module not accredited for use with this unregistered FSUIPC

Hmm, those are certainly the correct details for the program as notified to me, so the Key should work -- if it is built into the program, as it should be.

In order for me to determine whether it is writing the key correctly, could you repeat this test, exactly as above, only before loading FlightTracker go into the FSUIPC options (ALT M F), find the Logging page, and enable IPC read and IPC write logging. Keep the session short again.

Remember to turn off the extra logging next time you load FS or it may make rather large files.

If the Key is not built into the program then I can only assume either that it is an older version, or that the author intended that user's should manually enter the key. But then the latter would be published with the documentation.

Since the Key was issued way back in July 2003 and this is the first such inquiry I've had, I can only assume something is wrong with the specific package you have. However, let me see the fuller log, then we will know and you can be more specific when you request support from the suppliers.

Regards,

Pete

[Trevor Brooke]

Here is the log.

********* FSUIPC, Version 3.41 by Pete Dowson *********

Running inside FS2004(original release)

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Module base=61000000

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

WeatherOptions(Orig)=0000B027[0000B027]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=0

10846 System time = 07:09:51

10876 \\TREVORBR\Program Files\Microsoft Games\Flight Simulator 9\

10896 System time = 07:09:51, FS2004 time = 12:00:00 (00:00Z)

21311 FLIGHTS\OTHER\FLTSIM.flt

21461 AIRCRAFT\c172\Cessna172SP.air

22943 Aircraft="Cessna Skyhawk 172SP"

42972 Advanced Weather Interface Enabled

49051 C:\Documents and Settings\Trevor\My Documents\Flight Simulator Files\UI generated flight.flt

49562 Clear All Weather requested: external weather discarded

104921 WeatherOptions set, now 0000B027 (timer=0)

104921 LogOptions changed, now 0000000D (LogExtras=0)

126262 Client Application: "FlightTracker" (Id=1684)

126262 D:\Program Files\FS FlightTracker\FlightTracker.exe

126372 Product="FS Flight Tracker"

126372 Company="K. D. Lovell"

126382 READ0 3304, 4 bytes: 00 00 11 34

126382 READ0 3308, 4 bytes: 07 00 DE FA

126382 WRITE0 (failed, read-only!) 330A, 2 bytes: 00 00

126512 Illegal read attempt: offset 023E, size 2

126512Program or module not accredited for use with this unregistered FSUIPC

128074 ### IPC Message processed in 1562mSecs ###

128094 Illegal read attempt: offset 0240, size 2

128155 Illegal read attempt: offset 3E00, size 256

128165 Illegal read attempt: offset 3C00, size 256

128195 Illegal read attempt: offset 3BFC, size 4

128195 Illegal read attempt: offset 0609, size 1

128205 Illegal read attempt: offset 0AEC, size 2

128225 Illegal read attempt: offset 0020, size 8

128235 Illegal read attempt: offset 0564, size 8

128265 Illegal read attempt: offset 056C, size 8

129717 Illegal read attempt: offset 0BC8, size 2

129737 Illegal read attempt: offset 0366, size 2

129747 Illegal read attempt: offset 05DC, size 2

129757 READ0 3308, 2 bytes: 07 00

129777 Illegal read attempt: offset 023B, size 3

129787 Illegal read attempt: offset 0238, size 3

129807 Illegal read attempt: offset 0B74, size 4

129817 Illegal read attempt: offset 0B78, size 4

129847 Illegal read attempt: offset 1244, size 4

129857 Illegal read attempt: offset 1248, size 4

129877 Illegal read attempt: offset 124C, size 4

129887 Illegal read attempt: offset 1250, size 4

129907 Illegal read attempt: offset 0B7C, size 4

129917 Illegal read attempt: offset 0B80, size 4

129947 Illegal read attempt: offset 0B84, size 4

129957 Illegal read attempt: offset 0B88, size 4

129977 Illegal read attempt: offset 0B8C, size 4

129987 Illegal read attempt: offset 0B90, size 4

129997 Illegal read attempt: offset 0B94, size 4

130017 Illegal read attempt: offset 0B98, size 4

130027 Illegal read attempt: offset 0B9C, size 4

130047 Illegal read attempt: offset 0BA0, size 4

130057 Illegal read attempt: offset 0BA4, size 4

130087 Illegal read attempt: offset 0BA8, size 4

130087 Illegal read attempt: offset 1254, size 4

130117 Illegal read attempt: offset 1258, size 4

130127 Illegal read attempt: offset 125C, size 4

130147 Illegal read attempt: offset 1260, size 4

130157 Illegal read attempt: offset 0AF4, size 4

130207 Illegal read attempt: offset 30C0, size 8

130217 Illegal read attempt: offset 023E, size 2

130238 Illegal read attempt: offset 0240, size 2

130258 Illegal read attempt: offset 023B, size 3

130278 Illegal read attempt: offset 0238, size 3

130828 Illegal read attempt: offset 0BC8, size 2

130848 Illegal read attempt: offset 0366, size 2

130858 Illegal read attempt: offset 05DC, size 2

130868 READ0 3308, 2 bytes: 07 00

130888 Illegal read attempt: offset 023B, size 3

130898 Illegal read attempt: offset 0238, size 3

130929 Illegal read attempt: offset 0B74, size 4

130929 Illegal read attempt: offset 0B78, size 4

130959 Illegal read attempt: offset 1244, size 4

130969 Illegal read attempt: offset 1248, size 4

130989 Illegal read attempt: offset 124C, size 4

130999 Illegal read attempt: offset 1250, size 4

131029 Illegal read attempt: offset 0B7C, size 4

131039 Illegal read attempt: offset 0B80, size 4

131059 Illegal read attempt: offset 0B84, size 4

131069 Illegal read attempt: offset 0B88, size 4

131069 Illegal read attempt: offset 0B8C, size 4

131099 Illegal read attempt: offset 0B90, size 4

131109 Illegal read attempt: offset 0B94, size 4

131129 Illegal read attempt: offset 0B98, size 4

131139 Illegal read attempt: offset 0B9C, size 4

131169 Illegal read attempt: offset 0BA0, size 4

131179 Illegal read attempt: offset 0BA4, size 4

131199 Illegal read attempt: offset 0BA8, size 4

131209 Illegal read attempt: offset 1254, size 4

131229 Illegal read attempt: offset 1258, size 4

131259 Illegal read attempt: offset 125C, size 4

131269 Illegal read attempt: offset 1260, size 4

131289 Illegal read attempt: offset 0AF4, size 4

131329 Illegal read attempt: offset 30C0, size 8

131339 Illegal read attempt: offset 02BC, size 4

131369 Illegal read attempt: offset 023E, size 2

131369 Illegal read attempt: offset 0240, size 2

131399 Illegal read attempt: offset 023B, size 3

136426 Illegal read attempt: offset 02C8, size 4

136436 Illegal read attempt: offset 0574, size 8

136456 Illegal read attempt: offset 023E, size 2

136466 Illegal read attempt: offset 0240, size 2

136497 Illegal read attempt: offset 023B, size 3

136507 Illegal read attempt: offset 0238, size 3

137017 Illegal read attempt: offset 0BC8, size 2

137027 Illegal read attempt: offset 0366, size 2

137037 Illegal read attempt: offset 05DC, size 2

137057 READ0 3308, 2 bytes: 07 00

137067 Illegal read attempt: offset 02C8, size 4

137097 Illegal read attempt: offset 0238, size 3

152149 LogOptions changed, now 00000001 (LogExtras=0)

169764 System time = 07:12:30, FS2004 time = 07:10:34 (15:10Z)

169764 *** FSUIPC log file being closed

Memory managed: 94 Allocs, 142 Freed

********* FSUIPC Log file closed ****

[Trevor Brooke]

Thanks for the help Pete. I went looking for the key on the program's website and found it. I'm not sure why it wasn't built into the program, and I haven't tested it yet (no time right now), but I think it should work, right?

[Pete Dowson]

126262 Client Application: "FlightTracker" (Id=1684)

126262 D:\Program Files\FS FlightTracker\FlightTracker.exe

126372 Product="FS Flight Tracker"

126372 Company="K. D. Lovell"

126382 READ0 3304, 4 bytes: 00 00 11 34

126382 READ0 3308, 4 bytes: 07 00 DE FA

126382 WRITE0 (failed, read-only!) 330A, 2 bytes: 00 00

126512 Illegal read attempt: offset 023E, size 2

126512Program or module not accredited for use with this unregistered FSUIPC

Well, there's no attempt whatsoever by the program to provide a Key.

Please re-check the documentation. Possibly the author intended users to enter the Key manually. Else, either it is the wrong version (possibly an FS2002 version?) or a mistake has been made by either the suppliers or author. Please feel free to cut and paste this entire message and send it to them in your request for assistance.

If I can find the author's email, I will point him to this thread as well,

Regards,

Pete

[Trevor Brooke]

Thanks for all the help Pete. It works now.

[Pete Dowson]

Thanks for all the help Pete. It works now.

What was wrong? Was it a manually entered key, listed in the documentation?

Regards,

Pete

[Trevor Brooke]

Check out the post right above your analysis of my second log. :D Yes, it was a manually entered code. I was told that it would have automatic access, but obviously not. I went looking for the code, found it, and now it works. It's all good. :)

[Pete Dowson]

Check out the post right above your analysis of my second log.

Ah, sorry. Missed that. Easily done when you are only looking at additions to the end of the thread -- your earlier one must have crossed with mine.

Anyway, glad it is sorted. Shame it isn't automatic though.

Regards,

Pete