Pete Dowson

Well, if it worked with TAB, it should work okay normally, because the way it operates on "TAB" is the same as when it operates after you assign it and use it. So, something else may be wrong. You could try enabling the Button and Key logging facilitiy (FSUIPC logging options) and see what that reports when you atrtempt to use the button you programmed. After that, perhaps you need to show me the relevant [buttons ...] sections of your INI file, and the [MacroFiles] section, and the Macro file you refer to as well. I will also need to know the version number of FSUIPC. Regards Pete

That document gives updated status for FSX. The base document from which it derives and which covers all versions up to FS2004 is called "FSUIPC for Programmers". Regards Pete

I shouldn't think so, but you have to ask SimMarket. I have nothing to do with that part. I only do development and tech support. Regards Pete

Strange. I've never heard of any problem, ever, with registering on XP. As far as I am aware, FS does not need Administrator privileges to update the registry. It certainly doesn't on my systems. Maybe it is a function of one of the versions of XP I've never seen? Hmm. I never get asked for a password, but then I installed XP myself and didn't set a password. It sounds as if whoever set up your computer installed things with a password. No one has to be called "Administrator". That is not a person's name, just a privilege level. If you are genuinely the administrator for your PC and can create and delete accounts without using a password, how is it you cannot run a program as administrator without a password? Won't it accept nothing as password (i.e. simply press Enter)? If the folks who set up your system set it with things locked by password you may need to ask them what passwords they used. Regards Pete

It is Zipped with a version of Winzip which is compatible with all versions I know of, at least back to 8, and it is also compatible with the unzipper built into Windows XP, Vista and Windows 7. It is certainly also file-typed as a ".zip" file, so any version of Winzip should either recognise it, or, if your download is corrupted, at least say it is a bad or corrupted zip file. Check that your anti-virus or other protection programs haven't actually prevented the proper download, or even renamed the file. Regards Pete

It is nothing to do with accounts. Just right-click on the FS icon, select Run As Administrator (sometimes as one line, like that, sometimes as "Run As" then select Administrator, depending on version of Windows). Don't mess with account names. Pete

Please do NOT use the FSInterrogate parameters as documentation for offsets. I cannot support such use. To start with they are likely to be out of date and even incomplete, and second they simply do NOT contain so much explanation. All of the assistance I provide is in the offset documentation, which you should ALWAYS use. The FSI files are simply an aid to debugging your code when interfacing to FSUIPC. 0D0C has ten bits, one for each of 10 lights. When its bit is set to "1" its corresponding light is on. When it is "0", it is off. Simple. Just like a switch. If you are programming in such an advanced language then surely you understand bits and bytes? Regards Pete

Could the other yoke be "jittering"? i.e. sending small changes even though you don't think you are moving it? If so, then it sounds like you have both enabled but not being arbitrated. With all recent versions of FSUIPC, if you assign in FSUIPC Assignments and selected the "direct to FSUIPC calibration" option when assigning, then FSUIPC arbitrates between the values being received and only accepts the one supplying the largest deflection. I'm afraid I cannot really picture what you are experiencing from this description. Regards Pete

Aha! Glad you found the solution! Pete

With FS2004 and before you can disable the text using the option on the first (About) tab in FSUIPC options. With any version of FS the only way I know to stop the voice is to do so in the Options-Settings=Sound menu. One of the sliders affects ATC voicing. Pete

If it worked before you registered, but not after, then there's only two possible explanations: Either (a) your system date, the one Windows knows, it set to BEFORE the date you purchased the registration, making it look invalid, OR (b) the registration key you are trying to use is, indeed, a forgery, an illegal one made by a pirate key generator. Hopefully you are a legitimate user who has merely forgotten to set his system date (and maybe time?) correctly? Regards Pete

I am using WideFS from a Win7 64-bit FSX server PC. There's absolutely no difference. It works in exactly the same way. You are most certainly making an error. There is no way any of the Registration processing is any different between 32- and 64-bit and your registration of FSUIPC4 proves that -- it is the same identical code doing both FSUIPC4 and WideFS7. When it "doesn't accept the key", what exact message does it show, and where? Please show me the Install log for the Registration Install. If WideFS is "marked as registered" your key most certainly could not have been rejected as you say. And when the message "waiting for clients" disappears, what replaces it? There is no mechanism for simply removing it. I'm afraid your report is not making any sense to me as it stands. In fact it conflicts with itself. I need to know exactly what messages you are seeing, and where. And I need to see the Install log, the FSUIPC4 log and the WideServer log files, all from your FSX Modules folder. You can paste them into a message here, they will be short enough. Regards Pete

Error 10 cannot occur on the _Open request, only on the _Process request. As you can see, it is defined in FSUIPC_User.h as follows #define FSUIPC_ERR_NODATA 10 // Call cannot execute: no requests accumulated so it simply means you are executing an FSUIPC_Process() call before adding any Reads or Writes. This is confirmed immediately on inspection of your code: What do you expect that Process call to do, immediately after the Open and no Reads or Writes to process? Please do think more about the meanings of the error numbers. It will help you understand your bugs. Regards Pete

No, it is not common. It is rare. It means, as it says, that the version of FSUIPC you have installed is too old for the version of FS you are running (FS9.1). Naturally, versions of FSUIPC written so long ago do not know about later versions of FS -- that is all the message says. Such old versions of FSUIPC are no supported in any case. You should ALWAYS check for and update to the latest version before asking for support. In this case, replacing your 5 or 6 year old version with one made just a few weeks or months ago, will fix your problem. Seems that it a bad product which was not only made before FS9.1 was released, which makes it pretty old in any case, but also doesn't even bother to check whenther it is replacing a later version of FSUIPC with a much older one! Very bad! :-( It is absolutely impossible for that message to appear with any recent version of FSUIPC. Therefore you are not looking at the correct FS Modules folder at all. Either you have duplicate FS installs and you are messing with the one you are not loading, or you are using Vista or Windows 7 and have FS installed into its default "Program Files" location. That in itself is a big mistake, as it makes it not only difficult for you in cases like this, but it also makes it doubly difficult for most add-ons to either install correctly or run correctly. This is because Vista/W7 protects all Program Files folders from being written to by any program or user who is not running in "elevated administrator" mode. Because FS2004 is non-Vista aware, and Vista recognises this, it creates "aliassed" folders -- the ones you can see and write to are NOT the ones it is actually using when running. In order to see those and manipulate their contents you will have to run Explorer in Elevated Administrator mode (find its icon, right-click and select "run asadministrator"). Regards Pete

Did it work when you tested (via TAB) before naming it? If not, then the aircraft gauge concerned is probably simply not amenable to the way FSUIPC intercepts and handles the calls. No, sorry. I don't have all of the add-on planes one can get and I cannot undertake to test them all. The mouse macro facility is provided for you to try. If it works, great, if it doesn't it is unfortunate, but there's nothing really I can then do. It is quite easy for Gauge programmers to write gauges in a way which prevents the macros from working -- this is why you must always run the TEST as instructed. Note that almost all of the default (Microsoft-written) gauges are not amenable to mouse macros either -- Microsoft did not follow their own rules in writing those gauges! The only way might be to use something like Luciano Napolitano's "key2mouse" program to convert keypresses to mouse actions, and then program the buttons to send the keypresses. Regards Pete

Yes, it was very clear, thank you. Evidently you didn't understand my reply, though? Yes, understood. You can do it but with 10 copies of WideClient, not one, each connecting to a different server, and each client with a different value for "ClassInstance". Yes, though they don't need visible Windows. Your program would have to open ten links, one each to the 10 different Class Names. I'm afraid I cannot help further now till I return next Tuesday. Regards Pete

You are welcome. Glad it is all sorted. Regards Pete

The problem is that the interface to FSUIPC works by programs interfacing via FS's Window, using its classname "FS98MAIN" (don't ask why it is named that -- it has stuck since FS98). WideClient creates a Window with the same class name so that FSUIPC clients still interface correctly. You cannot have multiple top level windows with the same classname and have unambiguous connections to them. Therefore, FS and WideClient refuse to run if that ClassName is already used. There is a way, though, but you have to do some programming trickery. WideClient can be run multiple times on the same computer by use of different values for the "ClassInstance" parameter in its INI file. This even allows it to run alongside FS on the same PC. Please look this up in the WideFS technical document. You'd then have to write your program to connect separately to each of the different Window classnames. This means not using the FSUIPC SDK's code as it stands, but modifying it to address the selected ClassInstance. Regards Pete

Yes, good. All you need now is a client running on a properly networked PC. ;-) Pete

Sorry, no idea, really. I would say that something else is interfering with the FS controls you mention, but if that was the case I don't understand why there's any time element there. Are you sure it isn't something overheating, or a power supply problem to the PFC throttle control system? Maybe you need to replace the power unit? You will probably need to contact PFC support for any further help, as it certainly sounds like a hardware problem of some sort, probably power. Regards Pete

Keypad? It sounds like a keyboard, or keyboard emulator. Doesn't it come with a driver which allows you to assign keystrokes? Pete

The message box only appears if your installed version is later than the one you are trying to install, but there's no failure implied. It sounds like you are clicking some close button instead, or else you are misreading the message and it is saying something is wrong! There's no way the Installer terminates there unless there's something drastically wrong with your FSX installation. Please make sure you ARE using the current installer, the one for FSUIPC version 4.52 (from http://www.schiratti.com/dowson ), and show me the Installer log, which will be in your FSX Modules folder. Pete

Your message seemed to terminate too early. "Goes of ..."? What did you intend to say? All you need to do, when offered the registration options (the window which says "REGISTRATION OF FSUIPC4 / WIDEFS7"), is check "Both" and "Just enter new registrations", then click OK, and you will be able to enter all the details for both. Pete

There's no way FSUIPC ever makes assignments by itself, but there was a known problem with the early firmware of the Saitek yoke where it was generating spurious button presses. I even added a facility in FSUIPC to deal with it -- look up "EliminateTransients" in the FSUIPC4 Advanced Users document. It cannot. But as well as trying that EliminateTransients option, you might want to try the most recent version of FSUIPC4 -- 4.526 from the Updates announcement above. Regards Pete

What manual tells you this? For FSX and FSUIPC4/WideFS7 you run the FSUIPC4 Installer. There is no "Register WideFS" button in the options in FSX -- only an Enable/Disable WideFS button for registered WideFS users. Please refer to the registration information in the FSUIPC4 user guide. If you have registered FSUIPC4 you must have been through it all, just do the same again but register both this time. Of course you must come here for help. It points you here on the SimMarket purchase page, and in my documentation, etc. It is I who is responsible for all the development and support, not SimMarket. They are my publishers. You cannot expect publishers to know the technical details of their products. Regards Pete