Problem FSUIPC 3.65

[von]

I have used the previous versions of FSUIPC (unregistered) in the past without a problem. Now, with new version 3.65 a message says it does not support the programs I have used for a long time with MSFS ver 9.1

So, I printed the following FSUIPC log.

I need to know what it means and what I have to do?

********* FSUIPC, Version 3.65 by Pete Dowson *********

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

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

2578 System time = 10:06:18

2625 C:\Program Files\Microsoft Games\Flight Simulator 9\

2625 System time = 10:06:18, FS2004 time = 12:00:00 (00:00Z)

2953 Client Application: "fs9" (Id=2456)

2953 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

2953 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

2953 Company="Microsoft Corporation"

8312 FLIGHTS\other\MEIGS.flt

8406 AIRCRAFT\c172\Cessna172SP.air

18140 Illegal read attempt: offset 0238, size 3 [P2456]

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

18171 Module [M1] identified = "ActiveRadar.dll"

18171 Module [M1] "ActiveRadar.dll" access registration is okay

18171 Illegal read attempt: offset 0238, size 3 [P2456]

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

73500 ### IPC Message processed in 55360mSecs ###

100984 System time = 10:07:56, FS2004 time = 10:06:27 (15:06Z)

100984 *** FSUIPC log file being closed

Memory managed: 759 Allocs, 759 Freed

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

Best Regards,

Vaughan Martell

[Pete Dowson]

I have used the previous versions of FSUIPC (unregistered) in the past without a problem. Now, with version 3.65 a pessage says it does not support the programs I have used for a long time with MSFS ver 9.1

What was the previous version of FSUIPC you were using? There's been no changes to most of the access permission checking at all for a long time, but, due to an error on my part, versions 3.6xx (before 3.65) included some debugging code not normally included, and some of the checks would have been by-passed until the Beta period expired (which it just has).

So, I printed the following FSUIPC log.

I need to know what it means and what I have to do?

The relevant part is this:

     2953 Client Application: "fs9" (Id=2456)
     2953 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe
     2953    Product="Microsoft Flight Simulator 2004 - A Century of Flight"
     2953    Company="Microsoft Corporation"
    18140     Illegal read attempt: offset 0238, size 3 [P2456]
    18140Program or module not accredited for use with this unregistered FSUIPC

This indicates either that there is an add-on DLL installed which is accessing FSUIPC incorrectly, or that the aircraft your are using contains a Gauge which is likewise accessing FSUIPC using entirely the wrong method. The fact that the error occurs so early (before the flight is logged as loading) tends to point towards a DLL (but not ActiveRadar which is okay).

Unfortunately, because it is accessing FSUIPC as if it is an external program (VERY inefficient and likely to cause many problems even with a registered FSUIPC), it is identified as FS9 itself, which it obviously isn't. There's no way for me to identify it -- you need to check through your add-ons and find the culprit by a process of elimination.

Regards,

Pete

[von]

Hi,

Thanks for the reply.

I was using version 3.615 this am (flying OK)

Aircraft = Level-D 767-300

Everything worked OK

I installed your new version 3.65 or old 3.60 and got the error box.

I get your error box, click OK and MSFS then continues to load.

What can I do to get your new ver 3.65 working.

I have not changed any gauges, no changes.

Months ago I added a gauge to open/close cargo and main doors.

Best regards,

Vaughan Martell

[Pete Dowson]

I was using version 3.615 this am (flying OK)

Aircraft = Level-D 767-300

Everything worked OK

I installed your new version 3.60 and got the error box.

I just tried going back to FSUIPC ver 3.60

Same error message when I start up MSFS

There's a lot of 3.60's there!? I thought you mentioned something about 3.65? I did explain the business about Beta version codes and 3.6xx, remember? But certainly if one worked this morning, the same one will work this afternoon -- there is no "memory" in FSUIPC's operations.

However, that would have been pure luck, a fluke. You have something illegally using FSUIPC in a completely wrong way. Usually these add-ons date back to FS98 days, or at least not much later, and just have not been correctly revised.

The log certainly did not show a 767 being loaded, but the Cessna, as shown:

8312 FLIGHTS\other\MEIGS.flt
8406 AIRCRAFT\c172\Cessna172SP.air 

If you've not added any gauges to the Cessna then it must be an added DLL which is causing the problem, as I suggested.

What can I do to get your new ver 3.60 working.

I have not changed any gauges, no changes.

Months ago I added a gauge to open/close cargo and main doors.

As I said, you need to find out which add-on is causing the problem. I cannot do that for you. It is a process of elimination -- look first in your Modules folder and remove each non-Microsoft DLL in turn till you find it.

I'm pretty sure ActiveRadar.DLL is okay, but just try removing that first, as a test. I have it here someplace too, so I'll try it now ...

[LATER]

... No, that's fine here.

Whatever is causing the problem for you is starting out by trying to read the time. Does that give you a clue at all?

I'd get more information from your log if you go to FSUIPC's Logging page and enable IPC Read and Write logging. Then close down FS and restart it so we get the logging right from the start. I don't know if it wil help, but it may do.

Regards

Pete

[von]

OK,

I am not a programmer but I will follow your instructions.

I went back to FSUIPC ver 3.615

Nothing else running

MFSS loaded OK

I do use FSTime, but it was not runningto be sure of everything I will:

Have NO ActiveSky, NO clock, NO RadarContact running. By the way, when I do run these modules they are always started after I load MSFS>

Start MSFS with FSUIPC ver 3.615, load a Level-D 767 flight that I have been flying for the past week. Then exit the MSFS and print the log.

Next I will install FSUIPC 3.65 again.

Then, do the same flight, print the log and send it to you.

Best Regards,

Vaughan Martell

[von]

Hi again,

Here are the two logs:

First flight results:

********* FSUIPC, Version 3.615 by Pete Dowson *********

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

User Name=""

User Addr=""

WIDEFS not user registered, or expired

Module base=61000000

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

WeatherOptions(Orig)=40003605[40003605]

First flight using FSUIPC version 3.615

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=0

1047 System time = 11:54:36

1047 C:\Program Files\Microsoft Games\Flight Simulator 9\

1047 System time = 11:54:36, FS2004 time = 12:00:00 (00:00Z)

1156 Client Application: "fs9" (Id=2432)

1156 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

1156 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

1156 Company="Microsoft Corporation"

5312 FLIGHTS\other\MEIGS.flt

5375 AIRCRAFT\c172\Cessna172SP.air

5562 Aircraft="Cessna Skyhawk 172SP"

9672 Module [M1] identified = "ActiveRadar.dll"

9672 Module [M1] "ActiveRadar.dll" access registration is okay

16047 C:\Documents and Settings\Vaughan\My Documents\Flight Simulator Files\LD-SAN-CD.flt

16172 AIRCRAFT\LVLD_B763\B767-300.air

16359 Aircraft="[DXT3] Level D Simulations B767-300ER - American_Airlines_N327AA_DXT3"

19625 Clear All Weather requested: external weather discarded

19906 Module [M2] identified = "B767at.GAU"

19906 Module [M2] "B767AT.GAU" access registration is okay

21000 Module [M3] identified = "B767Afds.GAU"

21000 Module [M3] "B767Afds.GAU" access registration is okay

21234 Advanced Weather Interface Enabled

27828 Traffic File #21 = "scenery\world\scenery\fslive"

42031 System time = 11:55:17, FS2004 time = 03:54:50 (10:54Z)

42031 *** FSUIPC log file being closed

Memory managed: 4 Allocs, 161 Freed

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

Second "same" flight using FSUIPC version 3.65 which gave the error bos before MSFS loaded.

********* FSUIPC, Version 3.65 by Pete Dowson *********

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

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

1000 System time = 12:00:06

1000 C:\Program Files\Microsoft Games\Flight Simulator 9\

1000 System time = 12:00:06, FS2004 time = 12:00:00 (00:00Z)

1109 Client Application: "fs9" (Id=4008)

1109 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

1109 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

1109 Company="Microsoft Corporation"

5250 FLIGHTS\other\MEIGS.flt

5312 AIRCRAFT\c172\Cessna172SP.air

8719 Illegal read attempt: offset 0238, size 3 [P4008]

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

8734 Module [M1] identified = "ActiveRadar.dll"

8734 Module [M1] "ActiveRadar.dll" access registration is okay

8766 Illegal read attempt: offset 0238, size 3 [P4008]

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

20000 ### IPC Message processed in 11281mSecs ###

26156 C:\Documents and Settings\Vaughan\My Documents\Flight Simulator Files\LD-SAN-CD.flt

26281 AIRCRAFT\LVLD_B763\B767-300.air

28969 Clear All Weather requested: external weather discarded

29234 Module [M2] identified = "B767at.GAU"

29234 Module [M2] "B767AT.GAU" access registration is okay

30266 Illegal read attempt: offset 0238, size 3 [P4008]

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

30328 Module [M3] identified = "B767Afds.GAU"

30328 Module [M3] "B767Afds.GAU" access registration is okay

30578 Advanced Weather Interface Enabled

37187 Traffic File #21 = "scenery\world\scenery\fslive"

64125 System time = 12:01:10, FS2004 time = 03:55:02 (10:55Z)

64125 *** FSUIPC log file being closed

Memory managed: 451 Allocs, 749 Freed

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

Best Regards,

Vaughan Martell

[Pete Dowson]

I went back to FSUIPC ver 3.615

Nothing else running MFSS loaded OK

Yes, because as I said right at the beginning:

"due to an error on my part, versions 3.6xx (before 3.65) included some debugging code not normally included, and some of the checks would have been by-passed until the Beta period expired (which it just has). "

In actual fact, the Beta period for 3.60 passed, but 3.615 will work till the end of July I think.

Have NO ActiveSky, NO clock, NO RadarContact running. By the way, when I do run these modules they are always started after I load MSFS

I am not talking about external modules (which all of those are examples of), but about a DLL or GAUge installed in your FS. It is NOT ActiveRadar.DLL, but some other DLL or GAU -- probably a DLL, as I explained.

You seem to be missing much of what I am saying! :-(

Pete

[Pete Dowson]

Hi again,

Here are the two logs

And both show the same problem:

1156 Client Application: "fs9" (Id=2432)

1156 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

1156 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

1156 Company="Microsoft Corporation"

1109 Client Application: "fs9" (Id=4008)

1109 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

1109 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

1109 Company="Microsoft Corporation"

As I keep telling you, this is a problem caused by a bad module or gauge. The only reason it doesn't cause an error message in 3.615 is because of the Beta nature of the release, as I have explaned at least twice before.

Pete

[von]

Hi,

I will try to send the log file as an attachment. It is too big and I think I cannot send it as a .LOG file

Found out I will have to ZIP it.

If I can find a file to zip it up on my PC I will send it to you

Vaughan

[Pete Dowson]

Hi,

I will try to send the log file as an attachment. It is too big and I think I cannot send it as a .LOG file

I don't even know if it will help -- you really really do need to look at your FS Modules folder and see how many non-Microsoft DLLs you have there.

Anyway, if you remove ActiveRadar.DLL from there before you start the log will be MUCH smaller -- that module is constantly reading 1024 bytes to get the I traffic locations. Just take it out and keep it elsewhere for the test.

Pete

[von]

Ok,

I got it now.

The Beta versions could by-pass errors.

Now I am seeing them. They were always there back to FSUIPC ver xx.

I am sorry I did not understand at first, second etc.

I will try sorting through the DLL's

But, in all the years I have used MSFS and FSUIPC I had not had a problem like this. So, it came as a surprise.

Best Regards, thank you very much for your time. And patients. Greatly appreciated. Signing out.

Vaughan Martell

[von]

Ok,

I found the dll that caused the problem.

Has to do with Go-Flight modules, which I have been using for couple of years.

The dll name is GFMcp2K4.dll

When I removed that file and its .INI file to a temp. directory then I did not get your error box when MSFS first started up.

I use the Go-Flight modules and their GF-MCP autopilot. The autopilot software was updated some time ago so their autopilot could be used with the Level-D 767

So, I have to figure out what I need to get to make your ver 3.6 work.

My guess .... probably a bad one, is that I need an updated Go-Flight DLL.

In that case, they would already know that there hardware will not work

with FSUIPC ver 3.6 without new Go-Flight DLL?

This is where things can get a little messed up if I do not know what versions work with what.

I know you have a DLL module for Go-Flight MPC (was it , PRO?) for users who have registered version of FSUIPC. I should not need registered, right?

Best Regards,

Vaughan Martell

[Pete Dowson]

I found the dll that caused the problem.

Has to do with Go-Flight modules, which I have been using for couple of years.

The dll name is GFMcp2K4.dll

That cannot be the one which came with the original GoFlight MCP, because that didn't use FSUIPC. It seems that the new one (is that for the MCP Pro?) does use FSUIPC -- but GoFlight have never asked for an access key, so I assume they require folks to register FSUIPC? Even if they had an access key it wouldn't work with the DLL encoded like it is -- they are using an incorrect method entirely!

Unless you upgraded to the MCP Pro I'd advise you to go back to the older version.

I use the Go-Flight modules and their GF-MCP autopilot. The autopilot software was updated some time ago so their autopilot could be used with the Level-D 767

Hmmm. It sounds like they started using FSUIPC then, in that case.

So, I have to figure out what I need to get to make your ver 3.6 work.

Not specifically 3.6 -- ANY version of FSUIPC. You were only "lucky" with 3.6xx because of the Beta parts in it. That module would fail with all versions from 3.00 onwards -- i.e. any version of FSUIPC which works with FS9!

You have two choices as far as I can see:

1. Get GoFlight to re-write the module so that it either doesn't use FSUIPC, or does use it but correctly and with an agreement with me for an access key.

2. Purchase a registration for FSUIPC. That will stop the message. it won't make the access they are using correct -- that is and always will be a bad method and may cause unpredictable problems. But you won't know what is causing them anyway.

In that case, they would already know that there hardware will not work with FSUIPC ver 3.6 without new Go-Flight DLL?

It is nothing, repeat, nothing to do with 3.6!! It is ALL versions for FS9!

This is where things can get a little messed up if I do not know what versions work with what.

You do not need to know anything about FSUIPC versions. If you are using FS9 you have this problem with that module. There are no two ways about it. Complain to GoFlight, please.

I know you have a DLL module for Go-Flight MPC (was it , PRO?) for users who have registered version of FSUIPC. I should not need registered, right?

I have no GoFlight module. I added support in FSUIPC and WideFS for the buttons on the new GF modules -- registered users have always had FSUIPC programming facilities for older GF modules.

As for whether you need to register FSUIPC to use GF hardware -- it sounds as if they are forcing you to do so, yes. Please contact them and sort it out.

Regards,

Pete

[von]

OK,

I will contact Go-Flight and see if the "bad" DLL actually belongs to them and what I need to do.

I really appreciate your help here.

Initially you mentioned a "bad" DLL may not even work with the registered FSUIPC.

When a non-software type like me loads a program onto the computer I assume all this stuff works together .. believe they say backward compatible. So, the natural assumtionI just try to keep all the software up to date and that should do it.

Because your version was just loaded I assumed it may have a problem.

I learned a lot here Pete. Your time was not wasted and I hope in my heart this post saves another user and you some time down the road.

Best Regards

Vaughan Martell

[Pete Dowson]

OK,

I will contact Go-Flight and see if the "bad" DLL actually belongs to them and what I need to do.

The GFMCP DLLs are from GoFlight, of course. No one else writes drivers for their hardware.

Initially you mentioned a "bad" DLL may not even work with the registered FSUIPC.

The problem arises because if you ever have more than one such users (that DLL and, for example, a Gauge -- there are a few such around), they will both be using the same memory mapped file for the inter-Process communication (the IPC in FSUIPC) they are wrongly using. Thus one will corrupt the other quite readily. The results will be unpredictable.

The correct method for using FSUIPC from within the FS Process is a simple straight-forward recompilation using a different library and one small programming change. The correct methos is direct, efficient and safe.

When a non-software type like me loads a program onto the computer I assume all this stuff works together .. believe they say backward compatible. So, the natural assumtionI just try to keep all the software up to date and that should do it.

Sorry, the world is not perfect and not all software works 100% This is nothing to do with versions, just one incorrectly written module from GoFlight. By all means quote my messages from here if you like. It may help GF's programmer understand. ;-)

Regards

Pete

[von]

Ok,

I tried to register onto Go-Flights' boardhave not been able to yet.

So, I called them and left a message to call me.

In my previous posts I referred to your versions as old ver XX and it was typed wrongsorry.

Any reference I made to old should be like version 3.60 or 3.615

New version should have been 3.65

I went back and edited my errors on those posts.

In the meantime, I downloaded Go-Flights older software version that also has support for the Level-D 767.

I will try it soon and see what happens.

Thanks again for your help and understandingthru all my typos and confusion getting a grip on what's really wrong.

Vaughan Martell

[von]

Hi,

I purchased the registered version (3.65) of FSUIPC

All, the problems "went away".

Regards,

Vaughan

[Pete Dowson]

Hi,

I purchased the registered version (3.65) of FSUIPC

All, the problems "went away".

Yes, but they shouldn't have been there in the first place. I hope you at least sent details to GoFlight. They need to be aware they are doing things wrongly.

You will need to take care, also, that you don't use any other add-ons which access FSUIPC in the same way -- e.g. some of the older gauges knocking around. If two or more programs, internal to FS, try to access FSUIPC using the same external access method they share the memory-mapped file for data exchange and each one's requests and returns will corrupt the other's, leading to odd things occurring.

Regards,

Pete

[von]

Hi,

Thanks for the feedback.

I will continue "trying" to contact Go-flightthey are not answering their phone.

Regards,

Vaughan Martell

[Pete Dowson]

I will continue "trying" to contact Go-flightthey are not answering their phone.

Very few companies do support by 'phone these days. You need to report it by email or via their Support website/forum.

Pete

[von]

Hi,

Yes, I tried to register on their forum but it would not go through.

I will keep trying.

At first I thought you developers (various vendors) shared notes to keep compatible with each other.... to the extent possible.

I tried programming switches and buttons for the first time.

When I programmed a CH yoke buttons it all worked ok until I exited MSFS then restarted MSFS. The button assignments no longer worked. I read some of your manual .. sorted out a few thingslike some of the assignments in MSFS must be deleted proir to assigning the buttons/switches/keys within FSUIPC.

I ended up backing up my FS9.cfg then deleting itso I could start fresh.

I deleted the FSUIPC.ini to start fresh. Deleted the assignments in MSFS that I wanted to program with my very own "registered" FSUIPC ver 3.65 (proud owner here!).

Everything is working great so far!

I then looked into the new FSUIPC.ini file and seen how the buttons were coded with ASCII character decimal values, seen how the control codes were used (like C66079/C66080) for the flaps, and noted the difference in coding for shifted/unshifted keyboard keys are coded.

I will have to be alone with your manuals and a lot of coffee for quite some time.

From now on I am only making one change at a time, testing it and documenting the change (plus appropriate file backup) prior to fixing the next hole in the dam!

Thanks for the support, you have a great product here. As I recently mentioned in the response to a post I did on another forum (about yoke buttons), I said, it seems to me that FSUIPC "registered" is the final fix to the unsolved problems.

Time to go read the pages and get a good grip on all this.

Best Regards,

Vaughan Martell