Jump to content
The simFlight Network Forums

AirHauler and FSUIPC/WideFS problem ?


Recommended Posts

Hello everybody,

rather strange question I have (following discussing with Duncan from AirHauler): since quite some time now I use FSUIPC/WideFS without any problem (using f.i. FDC live cockpit, radar contact, wideview, etc etc etc.)

To be complete, I do have 4 computers talking to each other, running happily together with Win XP Pro (French version) and 3 Win XP Fam. Ed. (French version), all with SP3. I do have the Belgian local settings (i.e. "1.000,00" for decimal settings in stead of UK/US "1,000.00" settings, with "100 €" in stead of "£ 100" and french language date settings, i.e. "Lundi 2 janvier 2011" and not "Monday, january 2, 2011" and "jj/mm/aaaa" for 02/01/2011 and not "mm,dd,yyyy" for 01/02/2011).

Until now this did not pose a problem, except for some Abacus-soft (and solved with their help).

Like I said, I did not have a problem until I used AirHauler. When having AirHauler follow my flights my FS9 crashes ("FS2004 has to be shut down, if you were in the middle...we apologize..."). I do have FS9.1. When doing exactly the same flights -without AirHauler, but with all other extensions activated- I do not have any error.

AH (according to Duncan) should have US/UK settings but even then FS9 continues to crash. Duncan thinks it should be FSUIPC/WideFS that causes the problem....(but all other soft works) Does anybody have any ideas ?

Thanks ever so much,

All my best wishes to all of you,

Peter

Link to comment
Share on other sites

As a matter of fact, all my extensions work fine with versions FSUIPC as of v3.51 until 3.998 (I installed this one as well), EXCEPT with Airhauler, and that's what my question is about... the moment I start AirHauler (on remote machine through WideFS) a minute or so later FS9 crashes (even when I start AirHauler in the middle of a flight and it tries to connect to FS9)...

easy solution: no AirHauler, no problems....

Since AirHauler has an issue with local Belgian settings, I set them to UK/US settings, with English as local language, but in vain...

Link to comment
Share on other sites

It looks like air hauler is writing something to a offset that fs does not like. Duncan didn't provide a list of offsets his app writes to? If he has maybe you could log those offsets you may find the one that is causing the problem.

That being said you could always use the logging feature in fsuipc, then start air hauler and see if it tries to write to a offset which would give a bit of an idea to what's causing the issue.

Other than that I will leave this to Pete.

Cheers

Link to comment
Share on other sites

When having AirHauler follow my flights my FS9 crashes ("FS2004 has to be shut down, if you were in the middle...we apologize...").

Make sure you are using the latest FSUIPC3 (3.998q), then, after you get the error, go to the Windows error log and retrieve the details. (Right click "My computer", select "Manage" then System Tools-Event Viewer. The error will probably be in the Application section. Get the mofule name (DLL) in which the error occurred, and the address and error codes.

Also, see what Air Hauler was doing last in FSUIPC by using the ipc Write logging, as alaxus suggested.

Regards

Pete

Link to comment
Share on other sites

Hello Pete,

in the FSUIPC.1.log, I juste have this one error: 55250 ERROR: Can't change message filter: functions not available

in the FSUIPC.log, the last lines are (never an error):

5740969 WRITEex 6D60, 32 bytes: 41 69 72 48 61 75 6C 65 72 20 4D 65 73 73 61 67

5740969 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 WRITEex 3380, 127 bytes: 34 30 30 20 55 53 47 20 2F 20 32 2C 36 37 38 20

5740969 6C 62 73 20 46 75 65 6C 2C 20 32 2C 33 34 33 20

5740969 6C 62 73 20 6F 66 20 43 61 72 67 6F 20 4F 6E 20

5740969 42 6F 61 72 64 2E 0D 0A 0D 0A 50 6C 65 61 73 65

5740969 20 4F 6B 20 74 68 65 20 50 61 79 6C 6F 61 64 20

5740969 44 69 61 6C 6F 67 21 0D 0A 20 00 00 00 00 00 00

5740969 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 WRITEex 32FA, 2 bytes: 0A 00

5740969 WRITEex 0262, 2 bytes: 01 00

5741031 WRITEex 6404, 1 bytes: 01

5741469 READ0 0BE8, 4 bytes: FF 3F 00 00

5741469 READ0 0BEC, 4 bytes: FF 3F 00 00

5741469 READ0 0BF0, 4 bytes: FF 3F 00 00

5741469 READ0 0BF4, 4 bytes: FF 3F 00 00

and in the event viewer, I have (after having changed the ntdll.dll already with all the previous versions, this one is the original one)

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.3520, adresse de défaillance 0x000109d8.

but as you can see, it is never at the same address (examples for Win XP-SP3)

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00010a19.

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00011689.

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00010a19.

Does this make any sense to any of you ??

Thanks,

Regards,

Peter

Link to comment
Share on other sites

in the FSUIPC.1.log, I juste have this one error: 55250 ERROR: Can't change message filter: functions not available

Not relevant. Also ".1.log" files shouldn't appear unless you've been messing pressing 2new log2 buttons in the FSUIPC options screen.

in the FSUIPC.log, the last lines are (never an error):

I don't expect an error to be shown, only the last few thngs your "air hauler" was doing before FS crashed.

All this:

5740969 WRITEex 6D60, 32 bytes: 41 69 72 48 61 75 6C 65 72 20 4D 65 73 73 61 67

5740969 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 WRITEex 3380, 127 bytes: 34 30 30 20 55 53 47 20 2F 20 32 2C 36 37 38 20

5740969 6C 62 73 20 46 75 65 6C 2C 20 32 2C 33 34 33 20

5740969 6C 62 73 20 6F 66 20 43 61 72 67 6F 20 4F 6E 20

5740969 42 6F 61 72 64 2E 0D 0A 0D 0A 50 6C 65 61 73 65

5740969 20 4F 6B 20 74 68 65 20 50 61 79 6C 6F 61 64 20

5740969 44 69 61 6C 6F 67 21 0D 0A 20 00 00 00 00 00 00

5740969 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

5740969 WRITEex 32FA, 2 bytes: 0A 00

is Air Hauler displaying a message on screen, beginning "400 USG - 2,678 lbs ..." You can decode it from the above data if you like.

Then this:

5740969 WRITEex 0262, 2 bytes: 01 00

5741031 WRITEex 6404, 1 bytes: 01

merely pauses FS and does something in Air Hauler's own area.

The reads aren't relevant (I only asked you to log the writes anyway).

and in the event viewer, I have (after having changed the ntdll.dll already with all the previous versions, this one is the original one)

NTDLL.DLL is a core part of Windows and should certainly never be tampered with.

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.3520, adresse de défaillance 0x000109d8.

but as you can see, it is never at the same address (examples for Win XP-SP3)

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00010a19.

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00011689.

Application défaillante fs9.exe, version 9.1.0.40901, module défaillant ntdll.dll, version 5.1.2600.6055, adresse de défaillance 0x00010a19.

This all points to a driver problem, probably the video driver. It most certainly isn't an FSUIPC or Air Hauler problem. Since it occurs when Air Hauler is asking for a window to be displayed, the video driver seems the most likely. You need to find and install a better driver for your video card.

Regards

Pete

Link to comment
Share on other sites

I can understand what you say if there were any OTHER program that gave me this error... but this is not the case...

I "fly" years with FS9 and tens of dozens of add-ons (and it is true I did not change my computer for the last four years, having a Core2 Quad processor and a 9800GX2 video card)... never had the slightest problem... it is only recently (and then only with Air Hauler) that this error occurs...

Like I said earlier, if I do not use Air Hauler, I (and FS) do not have a problem...

Regards,

Peter

Link to comment
Share on other sites

I can understand what you say if there were any OTHER program that gave me this error... but this is not the case...

I can understand your feeling on this, but nevertheless I don't know any other way crashes occur in NTDLL. the fact that the addresses of the crashes vary so much do indicate that it is very timing dependent. if there were a true bug in one particular part of FS or FSUIPC or Air Hauler it would be at a more consistent address, and almost certainly not in NTDLL.

Like I said earlier, if I do not use Air Hauler, I (and FS) do not have a problem...

Seems best, then, if you are not willing to try to fix it via driver updates to stop using Air Hauler. I'm sorry, but there is really nothing else I can do for you.

Regards

Pete

Link to comment
Share on other sites

Just forgot to mention: I have 4 (four) computers with same problem, 2 Nvidia, 2 ATI-cards of different generations...that is why I am certain it is not the video-driver...

I think the NTDLL is a better option to take a look at... as i understand this is a communications layer for WinXP, and the combination of settings and "native" language could be an issue (french-belgian,us/uk mix). I will try your proposition as well...

Very big thanks in the meantime...

Regards,

Peter

PS I was already running in windowed mode, to cope more easily with multi-monitor setups

Link to comment
Share on other sites

  • 1 month later...

Hi Pete,

I recently installed Air Hauler but I get the following error message when I try to fly a selected job: "FSUIPC not found in FS installation! Please install it before trying to fly the jobs!". I am running MS Windows 7, I am running Air Hauler and FSX as Adminstrator, I have installed FSUIPC and it shows up in FSX Add-Ons. Do you know what the problem might be?

Thanks

Andy

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.