Pete Dowson

Is the subject "FSUIPC Window"? If not you've appended to the wrong thread. You should start one of your own. FSUIPC doesn't control anything in FS -- programs USING FSUIPC do the control. Stop using the add-ons you have, one at a time, till you find which one is controlling your autopilot. Maybe it is supposed to? Next time you ask a question please provide rather more information -- version of Fs, version of FSUIPC, registered or not, what add-ons you are using. Pete

Installing doesn't normally need extra privileges because anything of type .msi or with "install" or "setup" in the name gets elevated admin rights in any case. It is the RUN-TIME, not the installer, that will need to be at the same level of privilege as FS -- you must either run both normally or both "as administrator". To run a program with elevated admin rights you have to right-click it and select "run as administrator". There may be an option for this to always happen in its Properties. Pete

Well, also look in the FSUIPC Log file. If there's anything there looking suspicious, let me see it. You could even enable IPC read/write logging, to see if the program is actually managing to excvhange some information before failing. Note that I'm away from next Wednesday for 8 days. Regards Pete

You shouldn't be referring to the cockpit when the FSUIPC options dialogue is showing. It is a "modal" window -- meaning that when it is showing nothing else is happening -- including re-painting other Windows! It sounds like you are not following the instructions. After enabling Macro making mode, you exit (Ok) out of the options, as it says, then go about making the macros, or doing as you like even -- just as per instructions. When done making macros for that macro file, you go back into the options and turn the mode off! Please do follow the instructions a little closer and you'll be okay. Regards Pete

You shouldn't give up so easily. A lot of folks seem to use FS Commander okay. Won't their support help? Regards Pete

So, does it all now work? Well, FSUIPC is only part of FS once installed, so if that's run with privileges, so is FSUIPC. If FS was installed in, say, C:\FS9 (which is the sort of place I always install FS in -- usually on a different hard drive in fact, so it would be D:\FS9 -- then you'd not have any problems with running everything normally. It's the darned annoying protections in Vista which cause the ruckus! Regards Pete

Oh, I didn't read the report like that. sorry. I can't do anything with that -- if it isn't actually IN FSUIPC it may not be directly related in any case. Regards Pete

Hmmm. strange that it would crash in CFS1 and not CFS2. As fasr as changes are concerned there would have been almost nothing separating tohse compared to what's happened since. Give me the offset value in FSUIPC (i.e same details as before -- no need for pix), and i'll have another quick look. Regards Pete

Ah, well, you did not say that. :-( What exactly was the problem? If the registration is rejected outright then in 99% of cases it is because you made an error in the details being entered. All 3 fields must be exactly correct. The other 1% are the pirated keys which have been blocked. Regards Pete

The problem is only that it makes its folders protected. And in turn it means other steps are then needed for Add-Ons. It means just exactly what it says! I'll try slightly different words: because a program "run as administrator" cannot talk to a program NOT "run as administrator", any program you run which needs to talk to FSUIPC needs to be run at the same privilege level as FS -- i.e. you have to run all FSUIPC client programs "as admnistrator" too! FSCommander is an example of a program which talks to FSUIPC and therefore needs to be at the same privilege level. Sorry, I can't really explain more basically or simply than that. Is English not your first language? Maybe someone else can help with this? Regards Pete

I've had a quick look, and I think it may be the hooks added recently for mouse macros. I should have made that code dependent upon the version of FS being FS9, as I don't think those facilities have any chance of working in earlier versions in any case. Please try this interim version and let me know: http://fsuipc.simflight.com/beta/FSUIPC3909.zip Regards Pete

NEVER EVER publish all your details like that! it is an open invitation to pirates to publish them all over the Internet, and before long there will be hundreds of FSUIPC users masquerading as you. I shall probably have to disable those keys now! What makes you think you are missing anything? If you were originally inquiring here about only FSUIPC4 and WideFS7, then what on earth was the problem? I merely explained that FSUIPC4 + WideFS7 were not the same products as FSUIPC3 + WideFS6. But you've not changed products in any case! However, now I think you might need to re-purchase them in any case, having published them openly with all your details. Or appeal to SimMarket for replacements, see if they look kindly on such a flagrant violation of privacy. :-( Pete

1. The fix lies in getting working Video drivers. This is a well known problem with FS and some drivers on some video cards. You might be able to get around it by running FS in Windowed mode. 2. Your FSUIPC3 key applies to any installation of any version of FSUIPC3 on any of your systems. Please check the instructions -- to register under Vista you have to temporarily run FS9 "as administator". Regards Pete

The only reason for running "as administrator" (except when Registering FSUIPC3) is if you are (a) running under Vista, and (b) have let FS install into its default "Program Files" folder (ugh!), and © are running an external program which needs to access FS's folders. The problem is that Vista protects all Program Files folders! It installs FS9, which is not a Vista-aware program, into hidden folders so it can write to them itself, and shows the rest of the world "aliasses" instead. not the real folders! In fact you can only see the real folders in Windows Explorer if you run that "as administrator". In general, it is best never to install non-Vista aware programs into Program Files. However, assuming that's too late now ... ... Yes, you can get around it by running FS9 "as administrator". (Not FSUIPC itself, which simply becomes PART of FS9). But if you do this you must run EVERY FSUIPC-using accessory program "as administrator" too -- Vista actively prevents programs of different privilege levels from sharing data! Regards Pete

Okay. That certainly shows a crash in FSUIPC. It might be rather difficult to ever get FSUIPC3 working in CFS1 -- that is very old and I've really not been able to regression test the many FSUIPC changes over the 10 years of development on any of FS98, FS2000, CFS1 or CFS2. The earliest one I can easily test on here is FS2002. However, I'll have a quick look. I'm away after Easter, till the 25th. Pete

There's the problem. For some reason the use of the router is fooling Windows into translating the ServerName from "CIAN-PC" into the IP address 67.215.65.132, which isn't a valid Local network address. It is probably some setting on the router, maybe part of its firewall or address translation system. You could try setting the correct IP address explicitly in the client INI, instead of Servername. Regards Pete

The FSUIPC.ZIP file on the Schiratti site contains more than one file. It contains the User Guide, the Advanced User Guide and several other files too. How are you not seeing these? As the User guide points out, there's nothing to installing FSUIPC3 -- it's merely a matter of copying the DLL to the Modules folder. Just one simple step. That's it! There's only ever been an Installer for FSUIPC4 (for FSX/ESP), and that's only because several other more complex things need doing for those, specifically concerned with SimConnect. A "full install" consists of copying the DLL into the modules folder, exactly as documented. It has never been any different. By "abending" do you mean crashing? Regards Pete

Ah .. so you aren't deleting the calibration in the INI, but doing it by pressing the "Reset" button (so that it reads "Set") in the Calibration tab? This certainly suggests that the calibration is actually selected fro that aircraft. Maybe you've not made calibrations aircraft or profile-specific? If not, then the calibration part will be calibrating the FS controls (there being no direct FS assignments, as you've removed those, you said). I think your aircraft are using those FS controls, and they are being calibrated in FSUIPC because you have told it to. Merely making Axis Assignments aircraft or profile specific does not stop the calibrations working if you've not done the same there! Aircraft/Profile specific settings can be applied to Axis Assignments, Calibrations, Buttons and Keys. It sounds like you've made an attempt to make some specific changes, but haven't gone far enough. In particular the calibrations are normally closely associated with the assignments, so if you change one you should usually change the other. Regards Pete

If that is the case then you cannot be right when you say "no speedbrake is assigned to any throttle". Something is operating the speedbrake. The calibration is being applied if removing it fixes things. Why are you calibrating axes for aircraft which don't use them? Use Axis logging in FSUIPC to find out what. And review your [JoystickCalibration ...] sections. You are evidently getting mixed up regarding which does what if deleting entries does unexpected things. Same again. The calibration in one [JoystickCalibration. ...] section of the INI file cannot possibly affect the operation of that function if another [JoystickCalibration. ...] section is in use, as only one of them is read at a time, according to the aircraft or profile in use. If the calibration is enabled for that aircraft then it will certainly apply inputs on that axis. I don't need it for now, but look at it yourself. What aircraft or profile section are you having to remove the calibration for? If it is the one for the aircraft you are having problems with, then you are right to delete it -- if it isn't in use it should not be there! Regards Pete

FSUIPC4 and WideFS7 are new versions for FSX/ESP only. The completely different design of those recent Microsoft programs necessitated a complete re-write, so they are new programs, not simply updates of the old ones. Your purchase of FSUIPC3 and WideFS6 covers FS2004 and earlier only. Regards Pete

Okay. that's good -- you are up to date! And the module is fine, not corrupted. What are the "state version numbers"? Are you for some reason setting FS2004 to "run as administrator"? If you have you must also run FSMeteo and any other FSUIPC application program "as administrator", because Windows will not allow two programs of different privilege levels to share data in memory. At least, this is true of Vista. I'm not so sure about XP. If this isn't the cause of your problem then I'm afraid you must go back to Marc and ask him to examine his message more thoroughly, as your FSUIPC installation and its registration are perfectly good. Regards Pete

You told me what he said already. He did not say what the message meant. How am I supposed to understand his message? Why tel me his reply again? did you not even bother to try removing the KEY file as I suggested? And you still have not told me any version numbers. I cannot help you any more unless you do! I have no idea whether you are even talking about FS2004 or FSX or something completely different! Too big? What are you doing? Just load FS, wait till it is ready to fly, then close it! Do NOT switch any logging options on! Do NOT touch any options at all! The lgo will be smaller than most messages here. Just read it in notepad and cut-and-paste it into a message here!! Anyway, I will not reply further until you provide version numbers. You are ignoring most of what i tell you, so this is a waste of time! :-( Pete

Don't send anything yet. If it is a registration problem it can only be one of two things -- an illegal pirated registration Key, or a Key purchased AFTER the current date set on your PC (correct the date). Since FSMeteo does not need any registration in the first place, you can test by simply removing the FSUIPC KEY file from the Modules folder and seeing if that fixes the FSMeteo problem. I cannot help you any further until you give the information I requested -- i.e. version numbers and the Log file. I don't understand why you've ignored this request!? It is totally irrelevant. You are not reading what I've been writing! Thst is not my message! You must ask Marc what he means by his strange message. I cannot guess. Pete

FSUIPC does not need to be registered to run FSMeteo. I've no idea what is meant by that message -- why didn't Marc explain what the message meant? If you want support for FSUIPC you MUST state version numbers -- version number of FSUIPC, version number of FS. You could also show me the FSUIPC log file (just paste it into a message) -- you will find it in the FS Modules folder. That would certainly speed things up, else we could be exchanging messages for days! Please close FS first, then get the LOG file. Note that the oldest supported versions of FSUIPC are 3.90 (for FS2004 and earlier) and 4.50 (for FSX and ESP). Regards Pete

No. In general there aren't offsets for many controls -- even where there are, in most cases they simply cause FSUIPC to send the control for you. However, you can send any control you like, using its numerical equivalent (see the controls list in your FSX Modules folder), via offset 3110. Regards Pete