Pete Dowson

There's absolutely no difference in the 3.99 installer to the 3.98 installer, and it's only these last few days such problems have been reported. I really have no idea why. I'm just adding a check in the installer for the needed level of privilege so at least it tells folks up front that it won't work and to "run as administrator" (which so far has certainly worked for all but two users). Interestingly again, the FSUIPC4 installer is also identical, yet (so far) there have been no similar reports for that at all. The "option 5" you used is, according to all the technical references I've checked, the very same as simply right-clicking, selecting "run as administrator", then giving the appropriate permissions if UAC is enabled. It is supposed to be just a way of avoiding having to turn off UAC in order to stop the prompts. It is all very mystifying. I'm starting to suspect that some folks have got something screwed up somewhere inside Windows, maybe one of the automatic updates messing things up. I assume you have automatic updates enabled (it is by default)? Have you installed Windows 7 SP1 by any chance? I've held off on that for now as I've read reports of problems it causes for some applications. Maybe mine is one of them. If you are on Win7 SP1 i shall have to do the update I suppose. :-( Anyway, when I've got to the bottom of it I shall certainly try to make it easier, but meanwhile I'll have to just refer folks to that link, or reproduce its contents in the Installation guide. Thanks for getting back about it. Regards Pete

Thanks! Could you please post a copy of this into the FAQ subforum, so it is retained? (It'll scroll off pretty fast here). Oh, and please just correct "Simflyer" to read "simFlight" in the 6th line. I don't know what that is? something in Windows Update? Best Regards Pete

Okay. Found it. Apologies. The check for Version 1.1 of Prepar3D as opposed to Version 1.0 wasn't applied correctly in the place which sets the Mouse Macro hooks. It is fixed in version 4.70c of FSUIPC, which will be available as soon as I can build it. Please check later today. Regards Pete

How strange! I've got no code handle mouse buttons. Let me try it here ... Pete

Please refer to the other thread with the identical problem. It's a bit silly maintaining two or more identical threads. Thanks you. Regards Pete

I think with the stricter ways Windows works these days you can only run something "as administrator" if you are logged on as the PCs administrator. I've just done some tests with a Guest account on my Windows 7 PC and there is no way any program needing installation privileges can be made to run "as administrator" on that without a lot of complicated permission changes in User Accounts beforehand (using the admin account). I've no idea why this has changed since this time last year, but I suspect it's down to some of the updates Microsoft has been pushing out. [LATER] This might help: http://www.sevenforums.com/tutorials/11841-run-administrator.html Let me know, please. This is getting more and more worrying. Regards Pete

Well that's a very misleading message. It most certainly has NOT been cancelled by its issuer. I suspect you have at some time rejected SimFlight as a publisher. You'll need to rectify that in Internet Explorer. See the section entitled About FSUIPC Signature Errors in the FSUIPC Installation document supplied within the ZIP. Regards Pete

As I told someone else in a thread near here, I'm wondering if Windows isn't giving the Install_FSUIPC.EXE program the normal elevated privileges it accords installers. Can you re-run the Installer but this time right-click on it and select "Run as Administrator", and re-register once more? Let me know, please. This is rather worrying. I'm suspicious that there is some security setting or maybe a Windows update which causes programs with "install" in their names to no longer be accorded their needed privileges. NOTE: I just heard via email from one user with the exact same problem that this indeed did fix the issue. I will be amending the instructions once again. Regards Pete

Sorry, this is ambiguous. You say you cannot assign some functions, but when you do assign they don't work? Please clarify: which is it -- cannot assign, or can assign? If you can assign, what is the precise name of the control you are assigning, please? Also, what aircraft are you assigning for, and which switch or function, specifically, are you wanting to control? If you mean the FS controls called "DME1 Toggle" and "DME2 Toggle" they work on the default FS radio stack, but not on the little DME display built into the main panels. I don't think many of the main panel switches have FS controls which work, other than the autopilot and bug setting ones. Are you using Project Magenta? Which part of PM displays selectable DME values? Regards Pete

That way did actually require FS to be "run as administrator" and then closed and re-run normally, which was awkward and should certainly not be needed. The Installer does actually call upon the EXACT same code inside FSUIPC.DLL to do the job. I have just received confirmation from another with EXACTLY your problem and using the right-click "run as administrator" with the Installer most certainly worked for him, as it works here -- yes, with Windows 7 too. I am about to revise the Installation instructions to emphasize this. If it is really not working like that on your system I need to know more. Something you are doing is evidently not the same for some reason. Pete

Why not? What stopped the Installer? Er ... so you DID run something? Sorry, but I need more information like: -- what stopped you installing 4.70? Was there an error message, or what? -- what did you do to FSX to change the appearance of Add-Ons? -- Is there an Install log in the FSX modules folder? If so please paste it in a message here. -- is there an FSUIPC4 log in the FSX modules folder? If so please paste it in a message here. Regards Pete

No. Commands are just that, commands sent to FS via Windows "WM_COMMAND" messages, which is what FSUIPC will do when you assign them. FSUIPC offsets are values in memory representing assorted quantities stored inside FS. You are mixing the two, which isn't logical. If these commands are specific to a particular add-on aircraft they are processed by code inside the add-on itself. FS won't know anything about them or whatever data they might manipulate, if any. And don't forget, actions, like switch changes, do not necessarily represent any data whatsoever. There is an offset provided by FSUIPC which you can use to send any FS command, along with a parameter if one is needed. That is 3110. Check it in the offsets table. That's about as close as you could get to driving commands via offsets. Regards Pete

They look okay apart from the Registration not being seen in FSUIPC. I'm wondering if Windows isn't giving the Install_FSUIPC.EXE program the normal elevated privileges it accords installers. Can you re-run the Installer but this time right-click on it and select "Run as Administrator", and re-register once more. Let me know, please. This is rather worrying. I'm suspicious that there is some security setting or maybe a Windows update which causes programs with "install" in their names to no longer be accorded their needed privileges. Regards Pete

That is because you need to re-register, via the Installer, when moving to a new PC, or reinstalling Windows. It does say this in the documentation. Show me the Log file please. Maybe the date on your new computer is incorrect? Regards Pete

Version 4.60 is now over a year old and is not supported. It has been replaced by 4.70. Please update. What does it say a "virtual signature" is? There is a proper digital signature, which you can check by right-clicking on the EXE and selecting Properties - Digital Signature. Select the one shown and click "Details" and it should say it is okay. I've never heard of a "virtual signature" and most certainly nothing of mine has got one. Nevertheless, there is nothing in any Windows operating system which stops you running programs which don't have any signatures whatsoever. You must have met many of them. So, I suspect you are misreading or misinterpreting the error you are getting. You'll need to be more specific, please. But do so with 4.70 not 4.60! Regards Pete

Of course you can!!! Look again at the place where you programmed that switch one way. Do you not even see the place below where you can assign the "off" or "release" too? Switch up = on = press, switch down = off = release. No, it is identical. with a button, press=on, release=off. There is absolutely no difference. You can in either case program the on/press and the off/release. In both cases electrically they are identical too -- on = current flows, off = current does not flow. Mechanically the difference is that a toggle switch locks in place whilst a button does not. I think you must have skipped too much when you read the User Guide! ;-) Pete

Sorry, you need to check elsewhere. FSUIPC won't even be loaded till much later. Regards Pete

Don't wait too long. if you don't get a solution that way by early next week, get back to me. I'll have to add an INI file parameter to let you tell it to ignore writes to 7B91. Regards Pete

Well, if you get no joy get back anyway. So how do you manage: only using SB4's menus or dialogues? Why not try assigning a transponder standby/on button or switch via FSUIPC? After all that's why it's provioded. The log only shows 7B91 being set to 0: 1503101 WRITE0 7B91, 1 bytes: 00 As defined in the SB3 offsets definition, this sets "normal" mode: .It seems to be doing this constantly, every 2.3 seconds on average. So the question for OpenCockpits is: WHY? Doesn't it mention this anywhere in the documentation, or don't you get any? If it deliberately writes 0 to set mode normal, there must surely be a way of telling it to set standby too, when you need it to. Regards Pete

Ah, that's different. That's not what you said before! In that case what I think OpenCockpits has done is to drive the SB4 transponder directly via its SimConnect registered controls AND the FSUIPC offsets, so you are getting the double effect. Maybe they've done this so that their driver works with both SB3 in FS9 and SB4 in FSX -- precisely the reason FSUIPC was updated. Can you ask them about this? Maybe it is something they can handle? I really don't want to remove a facility which was requested and which is now used by a lot of folks. All I did was make an existing FSUIPC3 facility for SB3 also work correctly for FSX and SB4 so folks could assign hardware switches or buttons to control its transponder. Let me know if they won't do anything about it and I'll look to see if there's some sort of fiddle I can incorporate for you. I'd need a bit more information then, though, like a log from FSUIPC4 with IPC write logging enabled whilst you run the OpenCockpits driver. How are you operating the SB4 transponder with OpenCockpits BTW? I think i need a clearer picture. (The FSUIPC4 INI file is of course not relevant now you've told me your first statement about it was wrong). Pete

Well there's some assignment in your INI which is activating the added FSUIPC control to drive the Transponder mode. There are 4 new controls, added about 6-8 months ago: transponder on/mode c, Transponder standby, Transponder toggle, and Ident. These are assignable to buttons or keys in the FSUIPC drop-downs. (They are also provided in FSUIPC3 for SB3). It is obviously something in your INI file activating one of the new controls, because you said " If I remove the FSUIPC.INI fie and let it create a new file all is fine. ". This is why I asked you to show me the relevant Buttons and Keys sections of the INI file! It will be easy to correct if only you'd understand this.. As I already said, the SB4 facilities were not in FSUIPC 4.60a. I gave you my "ideas" in my last reply. You seem to have missed part of my response! :-( It should be so easy to fix in your INI file -- from what you've said it is all down to an assignment in there! Pete

There's no change which would do that which I can identify. It isn't a complicated facility. Do you mean you have a switch or button programmed to put it into On/ModeC and that works, but switching it back doesn't? If you don't mean that, what do you mean? Can you please tell me exactly which "previous version" you are talking about - do you mean 4.60a, or something between that and 4.669? The transponder controls for Squawkbox4 were added AFTER 4.60a, so if you have those programmed I assume you do actually mean one of the interim versions? So, you say how you have the transponder options programmed, please? Maybe show me the relevant Buttons or Keys section. Regards Pete

When you purchase a key for FSUIPC you purchase just that -- a key which unlocks the user facilities. There is no "registered" and "unregistered" version. And you do not purchase a specific version -- only FSUIPC3 (for FS9 and before) or FSUIPC4 (for FSX and later). The single purchase covers all updates -- and you are expected to keep up to date or you get no support. i can't support old versions. As of this week the oldest supported version of FSUIPC4 is 4.70. (Actually now 4.70b due to some last minute changes). When you install or reinstall FSUIPC, or register it, it changes nothing whatsoever in your existing installation. It merely opens the additional facilities for you. No settings are changed without you explicitly changing them yourself. No files other than the program itself and its documentation and supplied examples are changed except for the KEY file which records your registration. As am I . I don't think that necessarily means that things have to be too simple? Regards Pete

Hmmm. It's checked by default because that's how you need it to be normally. If it is held the "KEY UP's" aren't sent until the button is released. It sounds like your add-ons which don't like the default have difficulty if there's not an appreciable time between the Keystrokes being pressed and being released. That's unusual -- most applications only take notice of the "press" in any case. Nevertheless I'm glad it solved your "little problem". ;-) Regards Pete

If you wish -- it might turn out useful. I do have it on all the time, even in my cockpit. I don't think it noticeably affects performance. Regards Pete