Pete Dowson

The log shows everything is fine. FSUIPC4 is running quite happily. Nothing wrong. I think you are using Vista, right? And you have installed FSX in its default place, in Program Files. All of the Program files folders are protected under Vista, and I'm wondering if those programs, FDC and ACARS need to be able to access them and cannot? I know FDC uses FSUIPC, but does this ACARS application? Are you by any chance running FSX "as administrator" and not the other programs? Or perhaps vice versa? If so, then the problem will be that Vista does not allow programs running with different privilege levels to exchange data in memory, which is the way the FSUIPC works. You have to run everything the same way. Regards Pete

I still don't understand why, having found the problem, you have not simply corrected your original INI file and restored it as FSUIPC.INI in the Modules folder. You continue to make a lot more work by instead trying to adapt a default INI which you only did in order to find the problem! Please do consider doing things the EASY way, that is fix your original INI. Regards Pete

Dowson, actually, but Pete will do. The answer would be in the FSUIPC Log. That's the Installer log, which isn't relevant now you don't have an FSX loading problem. I'd need to see the FSUIPC4.LOG -- I did ask for both. Please show me the FSUIPC log -- make sure you close FSX first, please. Regards Pete

Okay, that's good. I don't understand. If you found the problem and fixed it, as you say, why isn't the rest okay? Just correct the error in the original INI file copy and use that. I notice these in the [General] section: ShortAircraftNameOk=No UseProfiles=No so you are not making good use of the facilities in FSUIPC? Not using shorter names, not using Profiles? Have you, by any chance, made a file with default [General] settings, not used the settings you had originally? since you have this: [Profile.Concorde] 1=Concorde BANC HiVC NoCabin 2=Concorde BANC LowVC Cabin I suspect you aren't using a corrected original INI, as you should, but the default INI without everything pasted back in. Regards Pete

FSUIPC does nothing you don't ask it to. So you have things programmed incorrectly somewhere. That confirms even more that you have something assigned wrong. I suspect you are missing something in your checking. Don't remove FSUIPC.DLL, only the FSUIPC.INI file (rename it FSUIPC.TXT, say), so when you reload FS everything reverts to default settings. This will prove that it isn't FSUIPC as such, but your settings. Then you can add settings back from your saved version (FSUIPC.TXT) by cut and paste. Do it a little at a time till you find the cause. You can do this without having to reload FS -- keep both files open for editing and use the FSUIPC Buttons and Axes and Calibrations tab "reload" buttons to get them re-read each time. Alternatively, leave the INI be and enable Button and Events logging. See the problems and check the logs to see which buttons or axes produce (or don't produce) the desired control events. If you don't understand the log, show it to me. What is a "complete re-install"? There's only the FSUIPC.DLL, which won't change, and the INI file, for which see above. Regards Pete Craig

There's nothing in FSUIPC4 which can do that. Can you provide more information on this "fatal error"? It means nothing on its own. There should be more data available in the error report. Have you yet tried loading FSX with FSUIPC4.DLL temporarily removed from the FSX Modules folder -- if not, do so. What happens then? Also, show me the FSUIPC4.LOG and the Install Log files from the FSX Modules folder. They are both ordinary text files you can find in the FSX Modules folder -- paste them into a message here. How can everything be loaded and ready to go if FSX has crashed with a fatal error? You aren't making sense here I'm afraid. It really is very unlikely to be anything to do with a change in FSUIPC version as there aren't any recent ones relating to anything in FSX, only user options and minor fixes in the user facilities, none of which would be relevant whilst FSX is loading. I suspect you must have changed something else at the same time. Regards Pete

Look in the process list, the second tab. There'll be just the one. Delete it before trying to load another. Pete

Yes, FSUIPC seems to detect other copies of FSUIPC already running even when they are in a different process. I don't know how -- but it looks the same internally as if there are two loaded. Use the Task Manager and forcibly close the FS9 process which has hung. Regards Pete

What does the =S signify? If you are Nicolas Baeza Castillo then both your keys are for the FSX versions, and both work fine. You are definitely making a mistake. Probably mixing up the 1's and I's I see in the Key. Use cut and paste if you aren't sure! Regards Pete

Well, I am using XP 32 here, on my usual Internet PC, and if I right click on a program or program shortcut I get, as the third item in the pop up menu, "Run as ...". then if I click that I get the options to run as "current user" (which is me, the only user), or "the following user" of which there is always at least "Administrator". Vista is, indeed, simpler here, with "Run as administrator" as one of the direct options. Well, you can do. I'll take a look. But I'm pretty sure it'll be deep in Windows someplace. Okay. Let me know. Regards Pete

There's no way to do that, sorry. There should certainly be no need in any case. Why not simply have your controls configured to be "aircraft specific" or "profile specific" -- FSUIPC assignments, calibrations, buttons and keys can all be specific to aircraft using the aircraft specific facilities or Profiles. Even if you are actually using the same aircraft for both situations, it would be easy enough to edit its AIRCRAFT.CFG file, make a copy of the relevant section in there with a different name, and have that specific. No, there isn't -- at least not for the same User. You could do it by installing FSX separately for two users and then swap by logging off and back one as the other. However, as I said, it really is completely unnecessary. You are simply not making full use of FSUIPC's flexibility. Regards Pete

Not merely from the clock/date being wrong, no. That only matters for Key validity. However, if the code signature on the DLL module is incorrect -- e.g. because the module has been tampered with or infected by a virus -- then it is possible the same problem could occur. A code signature failure will be reported in the FSUIPC LOG, and the user can check by looking at the file properties too. Otherwise, since it isn't my program reporting the message there's no way I can answer it 100%. It may have an error in its code which compares something against "3911" and decides it is too low for some erroneous reason. But it sounds most unlikely. Pete

FSUIPC will never interfere with any commands unless you've told it to. That's something you've set. Are you talking about Key or Button assignments here? Sorry, you really do have to be more specific. Nothing of what you say is making much sense. Okay -- I'll need to see the relevant Aircraft-Specific Buttons and/or Keys sections from the INI file, then. Evidently it isn't anything to do with Macros. Pete

That's not relevant. Right click on FS9, or the icon you use to run it, and select "run as", then explicitly select "administrator". This gives the program a higher level of privilege, called "elevated administrator" -- at least that's how it is on Vista. I don't really know XP 64 -- I avoided it because a lot of folks said it had many problems, especially with drivers. I switched to 64-bit with Vista, which is pretty good, but am now using the Windows 7 Release Candidate 64-bit version which, so far, I can say is really good -- faster than XP or vista. Nor has anyone else, judging by the complete lack of such reports until yours. This is why I'm suspecting something else interfering -- unless it's a real bug in XP 64. Regards Pete

Such reports only occur when users are either using invalid (pirated) registration keys, or ones sold AFTER today's date according to their computer's clock. Regards Pete

Version number of FSUIPC? Version number of FS? Can you show me the Macro file? Are you assigning both in aircraft-specific / profile modes and generically? You say: but, in fact, if the assignment has been duplicated even once, you could not possibly change it in FSUIPC options, you'd have to edit the INI file. I don't know what you have going on there, but I cannot help without even knowing which main version of FSUIPC you are using -- please check that it is up to date first. No less than 3.90 or 4.50 (there are later versions in the Updates Announcement too). Regards Pete

Well, This is a first. FS2004 and FSUIPC3 have been out now for nearly 6 years with no such problems. something is screwed up somewhere. The registration dialogue is a standard Windows dialogue using standard Windows API calls. No tricks, no nothing. It's quite astounding that normal run-of-the-mill standard Windows code could be unnrunable on one machine in thousands. Something is certainly clashing or interfering somehow. We need to see what's in the list of Processes which is causing this, maybe by a process of elimination. On thing to try first, if you haven't yet. I can't see what difference it makes on XP, but maybe XP 64 is different in this regard. Run FS9 "as administrator". That is right click it as select administrator. Regards Pete

"Probably"? Why not check the receipt/details on your SimMarket account? They've sent me nothing about any purchase for FSUIPC3 from Australia recently. Are you Michael Toohey? If so it was certainly for FSUIPC4 and you are simply making a mistake. I don't have anything directly to do with SimMarket. If you want to sort anything out with them you have to open your account and raise a problem ticket. Don't expect too much sympathy for buying the wrong product though -- they do make it very clear on the purchase pages. Regards Pete

Assuming you bought the right key (FSUIPC4 for FSX not FSUIPC 3 for FS9 and before) -- check that first -- you are most certainly making an error. You need to get all three parts -- name, email/address and key exactly correct. Careful with 1's and I's, 0's and O's, 2's and Z's. If you aren't sure, use cut and paste. Regards Pete

Yes, the FSUIPC.INI and FSUIPC4.INI files, for FS9 and FSX respectively. You should also backup your FSUIPC.KEY and FSUIPC4.KEY files, as these contain the registration details. If you ever have to re-format or even just reinstall Windows you will need to re-register, but it is easier with these files to cut and paste from. Regards Pete

That's always turned out to be a video driver problem in full screen mode. Try changing to Windowed mode first (ALT+ENTER). That seems to work every time --- so far. All that will be something else added -- many add-ons add the "modules" entry. Regards Pete

No, it means you have up to SP2 -- it does actually say that, see? "Acc/SP2" means Acceleration or SP2 (the Simconnect's are the same for both). It's just an abbreviation. And what is FSX doing when you are seeing zero? It does work. You should be using 3364 and 3365 together, BTW -- together (as a 16-bit word) they cover all cases. Regards Pete

Description? do you mean macro name? Most all text keys are assigned to one thing or another in FS -- it doesn't make any difference to FSUIPC as the keyboard is intercepted in FSUIPC before FS sees the keys. So whatever is trapping your "L" key is either doing it as a "Windows hot key" -- in which case it would probably still get it even if you went to a different program outside of FS -- or it is intercepting the keyboard in the same way as FSUIPC, but is doing so beforehand. The assignment to lights cannot be it, at least not the one in FS. So it has to be an assignment in one of your add-ons. If you cannot get around it, I suggest you use a different letter then Edit the macro name in the MCRO file before assigning it. Regards Pete

FSUIPC cannot have anything to do with graphics or textures. All the "stop moving" option does (assuming you've allowed it to work by setting Windows options correctly) is intercept "MOVE" and "SIZE" messages and discards them. All the texturing and drawing is performed directly between FS and your graphics subsystem. There's absolutely no graphics code in FSUIPC whatsoever. You've either got some bad add-on aircraft installs or a buggy graphics driver. Regards Pete

That's pretty old now, and unsupported. Please update to 4.50 at least. After installing 4.50 there's a replacement DLL (only) in the Updates announcement here, which will bring you up to 4.517 (or later depending when you look). It is best to always check that you are using the latest supported version before coming here with a question or problem. Check the "list of supported versions" in the Announcements. See the Logging tab in FSUIPC options. How else? Logging is controlled by Logging options in a tab labelled "Logging". It isn't so obscure. It is also actually documented! Pete