Problem with installing PFCFSX.dll

[selkan]

Hi again Pete, I have just completed another fresh install of XP64. I have installed FSUIPC and WideServer 4.5 (I actually decided to purchase new keys) no problem with this. However, when I went to install PFCFSX.dll I get the following warning window 'Problem! My signature check fails on the installed FSUIPC 4 dll. Please check that I am not listed as an "untrusted Publisher" in Internet Explorer (Int. Options-content-publishers)

You are not listed there as untrusted. If I start FSX, my PFC Console is recognised, and I am asked for my COM Port etc. However, if I then try and set up my Yoke buttons having first 'checked' show all FS Ctrl's', where I would normally get my drop down menus, the box turns blue, and after a couple of seconds, FSX stops working, and I get a warning window saying FSX has encountered a problem and needs to shut down.

I have tried only to put PFCFSX Version 4.3 on so far. I assumed changing the .dll to Version 4.3.4 wouldn't help?

Can you offer any advice

Thanks, Steven

[Pete Dowson]

Hi again Pete, I have just completed another fresh install of XP64. I have installed FSUIPC and WideServer 4.5 (I actually decided to purchase new keys) no problem with this. However, when I went to install PFCFSX.dll I get the following warning window 'Problem! My signature check fails on the installed FSUIPC 4 dll. Please check that I am not listed as an "untrusted Publisher" in Internet Explorer (Int. Options-content-publishers)

Erthe check on the installed FSUIPC4.DLL is carried out by the FSUIPC installer. All installing PFCFSX.DLL involves is copying the DLL into the Modules folder. There is no way possible that copying a file, using Explorer or whatever, will bring up a signature check on an unrelated module!

So, please explain what you are doing and where you are seeing the message!

You are not listed there as untrusted. If I start FSX, my PFC Console is recognised, and I am asked for my COM Port etc. However, if I then try and set up my Yoke buttons having first 'checked' show all FS Ctrl's', where I would normally get my drop down menus, the box turns blue, and after a couple of seconds, FSX stops working, and I get a warning window saying FSX has encountered a problem and needs to shut down.

Erhow does this relate to the stuff you said above? sorry, I'm not with this at all.

Can you offer any advice

Not without more information. Can you be a bit more explicit please? Can you show me the FSUIPC4 installer and run-time Log files, from the modules folder?

Regards

Pete

[selkan]

Hi Pete, firstly I copy over the following, which might be of help.

Installer for FSUIPC4.DLL version 4.40

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61472.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

Found later build SimConnect 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.500 found.

Installed version is later: it is not overwritten.

Looking for the current user's Application Data path:

... found as "C:\Documents and Settings\Administrator\Application Data"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Documents and Settings\Administrator\Application Data"

Found FSX.CFG in "C:\Documents and Settings\Administrator\Application Data\Microsoft\FSX\FSX.CFG"!

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Documents and Settings\All Users\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\Default User\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\LocalService\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\NetworkService\Application Data"

No FSX.CFG there

Now installing additional files into the Modules folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref FFFFFFFA)

Deleted GlobalSign Root fix programno longer relevant

All installer tasks completed okay!

Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

PFCFSX.ini

[General]

FlightAxisFilterLevel=75

PFCFSX.lof

********* PFCFSX.DLL, Version 4.30 by Pete Dowson *********

6281: Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

***** PFCFSX Connection Checks *****

FSUIPC is okay. All options available: 4.500

***** Retrying Connection Checks *****

COM3 open okay

MCP connection: PM Okay!

Aileron control Okay!

Elevator contrl Okay!

Rudder control Okay!

Thrttle quadrnt Okay!

***** Checks aborted before completion *****

25062: Refesh initialisation to synchronize switches

I will now try and go over what I am doing and what I see:-

Firstly, FSX is installed all O.K. I then use the FSUIPC Installer, this says all O.K. and asks if I want to Register, which I do for FSUIPC and WideServer.

I have now started FSX, and gone into the FSUIPC Menu (Alt,addons,FSUIPC) set up my requirements. I close FSX.

I now unzip the PFCFSX installer, and run the program. It says I have a later Version of FSUIPC and has therefore not overwritten. I then get the warning window about 'signature check fails'. I press O.K. on the warning window, and then looking at the Moduls Folder, the PFCFSX.ll has been installed.

I now start FSX, and at the same time turn on the Jetliner Console. After a couple of seconds, FSX stops, and I get the window asking me for my COM Port Number. I duely give the correct Number and go back into FSX.

Now I go back to the PFC menu (Alt, addon, PFC - FSUIPC is also still listed O.K>)

I set to the Jetliner Console, and place 737NG on the 'Main page', and place a tick in select aircraft automatically.

I now try to set up my 'buttons' on my PFC Yoke. On the Yoke page the FS Ctrls and PM Ctrls are NOT ticked; so if I now tick these boxes, I should get what is quite a long drop down menu on each tab. Normally I use these tabs for setting up different views to left right etc, but as soon as I press on a tab it turns blue, and FSX crashes, and I get a warning message/page saying FSX encountered a problem, and has had to stop.

You will notice that the information in the PFC ini appears to be very limited, as if not created properly.

You asked me to attach FSUIPC installer. Sorry, but I am not sure what you mean by this. If you mean the 'yellow' disk one double clicks in order to load the program, I am not sure I could attach that here?

I think that is all the info. I can offer for now. I did notice however at the end of the 'top section here' that it refers to the 'problem!' I am receiving.

Sorry this is so long winded.

Thanks, Steven

[Pete Dowson]

Hi Pete, firstly I copy over the following, which might be of help.

That's the install log I asked for. Okayso the INSTALL of FSUIPC4 failed!

Installer for FSUIPC4.DLL version 4.40

Why are you running the installer for version 4.40? It is NOT compatible -- the signature check will fail, because I've had to change the signature to that of simFlight!

Please run the Install FSUIPC4 program which comes with version 4.50, then show me the install log!

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref FFFFFFFA)

You should NOT try running FSX with that DLL until that problem is resolved.

I will now try and go over what I am doing and what I see:-

Firstly, FSX is installed all O.K. I then use the FSUIPC Installer, this says all O.K. and asks if I want to Register, which I do for FSUIPC and WideServer.

But you ran the Installer for 4.40 after you installed 4.50. I need to see the result of the 4.50 installer, not your later attempted install of 4.40..

I now unzip the PFCFSX installer, and run the program. It says I have a later Version of FSUIPC and has therefore not overwritten. I then get the warning window about 'signature check fails'.

This is where you are making no sense at all I'm afraid. There is NO installer for PFCFSX. You cannot possibly run it as it doesn't exist. PFCFSX is just a DLL which you copy into the Modules folder.

The fact that you got a message stating that you have a later Version of FSUIPC is only ever from the FSUIPC4 installer. You appear to be first running the FSUIPC4 installer for version 4.50 then the FSUIPC4 installer for version 4.40. PLEASE DO NOT DO THIS!

I press O.K. on the warning window, and then looking at the Moduls Folder, the PFCFSX.ll has been installed.

There is no program which installs PFCFSX.DLL for you. If there's a copy of PFCFSX.DLL there you must have moved it there yourself.

I repeat: THERE IS NO PFCFSX INSTALLER!!!

Please go back and run the installer for FSUIPC4 version 4.50. Then install PFCFSX.DLL manually, as it says in the user guide. Just copy it into the modules folder as instructed.

You asked me to attach FSUIPC installer.

No I did not! I asked for the Installer log -- please do read what I write. you did actually provide the installer log as I asked in any case, but foorgot the normal FSUIPC4.LOG, the normal run-time log which is the one showing what FSUIPC4 is actually doing.

Once I know you know what you are doing, which doesn't appear to be the case at present I'm afraid, we can proceed to looking at whatever the problem you have is. Until then it is rather pointless I'm afraid.

So, step by step:

1. Install FSUIPC 4.50 by running the 4.50 version of the FSUIPC4 installer.

2. Do NOT run any other program yet!!!

3. Install PFCFSX from the ZIP by copying across the DLL into the FSX modules folder.

4. NOW run FSX. Do NOT run the FSUIPC 4.40 installer again as you have been!

If you still get a problem, please assure me you are not running some other installer which I don't provide, and show me the two logs I asked for -- the FSUIPC Install log and the normal run-time FSUIPC4.LOG. I am not interested in your PFCFSX INI or PFCFSX.LOG files, they are not relevant.

Pete

[selkan]

Hi Pete, O.K. things are begining to make some sense, and infact I have things working! I hate to contradict you, but I got my PFCFSX drivers from FLYPFC, and that is a self install program. It tries to install FSUIPC first and then the PFCFSX.dll. That must be where the problem was. I deleated anything to do with PFC from my Moduls Folder and simply placed the .dll from your lastest build there (4.3.3 I think?) All then worked O.K. when I went to PFC Menus.

Just one other thing I hope you can help with please. We touched on this in my previous posts, but I shall start afresh here.

As you know, I have PFC Jetliner Console, but when I purchased I had the throttle quadrant replaced to represent a 737. I use the two lower buttons on throttles for TOGO, and normally the two 'side' buttons on the throttles for Auto Throttle Off. (which is actually printed on the 'handles'). I have in the past been able to set these buttons via FSUIPC 'Buttons and Switches Tab' However, when I go to this tab, there is a blinking cursor in the Box, but when I press my buttons which before would place a 'number code' here, nothing happens. In the past it would read something like #19etcetc, and then I could tick on FS and Include PM, scroll down and set A/T Off.

Is there a step by step process you can offer to help?

Thanks, Steven

[Pete Dowson]

Hi Pete, O.K. things are begining to make some sense, and infact I have things working! I hate to contradict you, but I got my PFCFSX drivers from FLYPFC, and that is a self install program.

Really? That's news to me. Sorry, but that is their doing. I cannot support their website, you need to go to their support. All my software is supplied in the Schiratti site or here, in the Announcements.

It tries to install FSUIPC first and then the PFCFSX.dll. That must be where the problem was. I deleated anything to do with PFC from my Moduls Folder and simply placed the .dll from your lastest build there (4.3.3 I think?) All then worked O.K. when I went to PFC Menus.

Can you report all this to PFC please, either via their direct support email or their forum.

As you know, I have PFC Jetliner Console, but when I purchased I had the throttle quadrant replaced to represent a 737. I use the two lower buttons on throttles for TOGO, and normally the two 'side' buttons on the throttles for Auto Throttle Off. (which is actually printed on the 'handles').

You have a version of the console which supports the 737NG cockpit throttle quadrant? Does it have detentes on the flap lever too? I didn't know they made any changes there at all -- they don't seem to tell me much! :-(

I have in the past been able to set these buttons via FSUIPC 'Buttons and Switches Tab' However, when I go to this tab, there is a blinking cursor in the Box, but when I press my buttons which before would place a 'number code' here, nothing happens. In the past it would read something like #19etcetc, and then I could tick on FS and Include PM, scroll down and set A/T Off.

In this past you mention, what was different? As far as I recall, the TO/GA buttons on the quadrant are only supported on the Jet cockpit. I wouldn't have supported them on the jetliner console because as far as I knew they couldn't exist! That's why I provided an option to treat the AT Disco buttons as TO/GA -- more valuable there because the AT arm switch is close to hand anyway (or is that removed from the console now?)

Maybe you told the PFC driver that you had a 737NG cockpit last time?

Really these are all things you should talk to PFC about. Especially if they change things without telling me -- I can't really offer support that way. Maybe you ought to mention this to them too, please.

Regards

Pete

[selkan]

Hi Pete, I will certainly write to FLYPFC, or as you suggest place something in their Forum. When I purchased my Console, now a little over four years ago, I was given the option of having a 737NG Throttle 'Unit', which I paid extra for. Yes, this does have Flap Detentes, and have never been a problem.

There is an A/T switch on my Console, but I have a PFC MCP (hardware), so for me it is better to turn the A/T off on this Unit (more realistic anyway)

In the past I was simply able to set my A/T Off switches (on throttle handles) in the FSUIPC 'buttons and switches tab', and it is that that I can no longer do. I hope I am making myself clear; on my throttle quadrant, there are two further buttons for TOGO or as you mention, can be used for A/T off if set on PFC Main Menu.

Anyway, all is now well thank you, and I shall report to PFC about these difficulties.

Thanks, Steven

[Pete Dowson]

Hi Pete, I will certainly write to FLYPFC, or as you suggest place something in their Forum. When I purchased my Console, now a little over four years ago, I was given the option of having a 737NG Throttle 'Unit', which I paid extra for. Yes, this does have Flap Detentes, and have never been a problem.

Amazing that they add these things and don't tell me! And if that was 4 years ago that was about the time I was adding the jet cockpit stuff, I think.

In the past I was simply able to set my A/T Off switches (on throttle handles) in the FSUIPC 'buttons and switches tab', and it is that that I can no longer do. I hope I am making myself clear; on my throttle quadrant, there are two further buttons for TOGO or as you mention, can be used for A/T off if set on PFC Main Menu.

I don't think you are reading my messages -- I did understand you perfectly as you will see. I also suggested this:

"Maybe you told the PFC driver that you had a 737NG cockpit last time?

Which you seem to have missed?

I most certainly haven't changed anything to do with any switches on the jetliner (or jet cockpit) for years, so I've no idea why you see any difference. If the hardware is okay, then it surely must be some setting you are omitting, such as the console selection?

[LATER]

I just checked my code. As far as I can see (I cannot test on your hardware from here), I do have code in place to send the switches to FSUIPC even if it isn't a jet cockpit selected. The differentiation comes AFTER the sending of buttons to FSUIPC. And, as I say, nothing has changed in this area for years -- and it's the same on PFCFSX.DLL as PFC.DLL.

Soare you sure the buttons are working correctly? Use "Test" mode in the PFC driver to see if they register on the right-hand side of that option page. Maybe the plug has come loose in the socket below the quadrant?

Anyway, all is now well thank you

So you did get the TO/GA buttons working? Can't you explain what you did to "fix" things, then, please?

Regards

Pete

[selkan]

Hi Pete, sorry, when I said all was working, I meant everything except the A/T Buttons. However, today I have achieved a work around and got them working! As you suggested, I went to PFC Test page, and the A/T Buttons were working, coding 00 and 01. As you know I have a separate A/T Switch on Console, and I wondered if they were interlinked in some manner. I went to the FSUIPC Buttons and Switches Tab, and when I placed this switch from off to On it registered a code 19 - 14 in the two available boxes. I then set the A/T to OFF in the PM drop down menu. When I then tried the A/T buttons on my throttles (with the console button left in on position), off went the A/T on the MCP into off/flashing mode.

So, everything this time is working, thanks again for advice, and I think we can now close this particular run of posts.

I did by the way post my difficulties to FLYPFC regarding their self install PFCFSX.dll (in their Forum)

Best wishes, Steven

[Pete Dowson]

Hi Pete, sorry, when I said all was working, I meant everything except the A/T Buttons. However, today I have achieved a work around and got them working! As you suggested, I went to PFC Test page, and the A/T Buttons were working, coding 00 and 01.

You mean 9C 00 (AT off) and 9C 01 (AT on) I think. The TO/GA buttons should give 9C 00 (off) and 9C 08 (on). The second value is actually a bit-field, so 09 would mean both on, and there are other bits used for anti-ice and EICAS switches.

Despite my statement that I understood, I have evidently misinterpreted pretty much most of what you said it seems. I thought all this exchange was concerned with the extra buttons you had on yours for TO/GA? From what you now say, it seems that this:

my A/T Off switches (on throttle handles) in the FSUIPC 'buttons and switches tab', and it is that that I can no longer do. I hope I am making myself clear; on my throttle quadrant, there are two further buttons for TOGO or as you mention, can be used for A/T off if set on PFC Main Menu.

was really meant quite literally -- that the TO/GA buttons, the lower ones, were actually being switched by my AT Disco / TOGA option! That is the complete surprise to me as that option is designed to switch the AT Disco buttons, not the TO/GA ones which normally don't exist on the Jet console.

Therefore I now believe the entire confusion is due to those two pairs of switches being plugged into the wrong sockets under the quadrant -- or at least, wrong in comparison with my understanding and how they are plugged in on the Jet cockpit. In other words the PFC driver is seeing your TO/GA buttons at the AT/Disco buttons and vice versa. This is why I said:

As far as I recall, the TO/GA buttons on the quadrant are only supported on the Jet cockpit.

and continued on discussing, to my mind, the supposed problems with your TO/GA switches! :-(

Never mindI'll harangue Eric about all this next time I see him!

Regards

Pete

[selkan]

Hi Pete, we seem to be at cross purposes. Lets start again! The lower buttons on my throttle quadant I use for TO/GO, and have never been any problem. The addition buttons; left and right of throttle handles (built into them) I use for A/T disconnect. It was these latter buttons that gave the Code 00 and 01; perhaps this indicates they were not working correctly?

So, as said in last post, I managed to 'link' these buttons via FSUIPC using the coding for the A/T on/off button on Console (just one switch next to throttle quadrant). Having done this, the A/T buttons on Throttle Handles now work; i.e. switch A/T to Off on MCP (which goes into flashing mode).

Hope I am now making myself clear?

Regards, Steven

[Pete Dowson]

The lower buttons on my throttle quadant I use for TO/GO, and have never been any problem.

As I understood only after the last message, yes.

Since my PFC driver doesn't support those buttons except on the Jet Cockpit, it definitely seems as if they've wired them to the same socket as the usual AT Disconnect buttons.

The addition buttons; left and right of throttle handles (built into them) I use for A/T disconnect. It was these latter buttons that gave the Code 00 and 01; perhaps this indicates they were not working correctly?

Codes are not single bytes. You mean 9C 00 and 9C 01 respectively I assume. This is the same code used for the AT Arm toggle switch. It is indistinguishable in the software.

Hope I am now making myself clear?

I thought I made myself clear in the last message, where it suddenly dawned on me, as I clearly said, that you were talking about the switches the other way around, and that, indeed, PFC had wired your switches to the reverse of what I would have expected, especially compared to the Jet cockpit, which is the only instance documented, or that I have seen, where both sets of switches are available.

I am clear on this now, but it seems you are still nowhere near convinced by my explanations?

I will have to tell PFC clearly that if they make such odd one-off (?) modifications without informing me, they must be prepared to support the driver nuances that arise. This has taken a lot of mine and your time needlessly. I am not amused.

This is finished now. Please, if you have any more queries pursue them with PFC.

Regards

Pete