Pete Dowson

Well 6.75 is the earliest version currently supported (as pointed out in the Announcements above). but WideFS has been working well now for 10 years, so I don't know how to answer that question other than "why not". However, why not simply download the current version? It isn't that big a package you know! I expect you'd get it quicker even than posting another message here! ;-) Pete

Ah, okay. thanks. I'll know now that GlobalSign was not included in Microsoft's Win2000 release. Regards Pete

Best to download WideFS.zip from http://www.schiratti.com/dowson and read the user guide. Pete

Ah! So the GlobalSign root data was not included in your Windows? I see from the Log: Isn't that Windows NT? Or Something else? I should remember that in case anyone else is still using an old operating system. Regards Pete

I don't think it could have said quite that, but I know what you mean. The installer cannot find the FSX.CFG file, which it needs to find so that it knows where to place the DLL.XML file. It looks like you've not run FSX yet, as that creates the folders and files needed. Try running FSX first, then exit and re-run the FSUIPC4 installer. Regards Pete

Yes. Otherwise FSUIPC is not writing anything of its own accord, so cannot smooth anything. Pete

Phew! What on Earth is it doing with all that processor time? That's crazy! This is not something I'm familiar with I'm afraid. I don't know even if this "sioc" uses the FSUIPC interface. If it doesn't then it won't run on WideFS. But if it does, then, yes, it using most of the other processor won't drag WideServer down on the FS PC. However, it might not work so well if it doesn't allow WideClient to get much processing time, to handle the networked connection. Have you asked on whatever support forum the "sioc" folks inhabit? For WideFS? On FSX you need the WideClient program from the WideFS package. For FS9 and before you need the whole WideFS package. It includes documentation. It doesn't work till registered in either case, and registration is separate for WideFS7 (on FSX) and WideFS6 (on FS9 and before). Regards Pete

Yes, of course, and it has been done. Where have you been these last 18 months? ;-) As far as the IPC facilities are concerned, that is exactly what SimConnect is. I was involved in SimConnect right from the start. It doesn't (yet) quite do everything that FSUIPC does, but it also, in some areas, does a lot more. Yes, he did, he's been working in the FS team since FS2000 days, but he's left now. He was not involved in SimConnect. His area of specialisation was graphics. Well, no, it was the other way around, ensuring that SimConnect was up to the job. The only reason it falls short in some areas is, well, time and money. As usual. Take a look some time at the FSX SDK. The SimConnect interface is quite well documented, and is being used more and more. ASX, TrackIR, the new PMDG aircraft, and so on, all directly interface to SimConnect, not FSUIPC. The FSUIPC4 application interface for FSX exists only for backward compatibility, to tide things over until all programs interface direct to SimConnect. This is why my development efforts in the last year have been almost entirely centred on extending the User facilities in FSUIPC, to make it worthwhile as a "Swiss Army Knife" type of toolkit for users. The demand for it to be used as an application interface is receding as SimConnect takes over. Regards Pete

I really have nothing to do with the SimMarket system. I know they don't accept "debit" cards, but credit cards should be fine. Have you raised a problem ticket with them? All I can do is forward your complaint to the Manager, in case there's a glitch in their system. [LATER] I forwarded the message and the Manager says he will take care of it via the problem ticket system, so please make sure you go through that procedure. Regards Pete

Yes, it was true at the time, but not now. I will re-word it. Thanks. Could you please tell me what action fixed it for you? Regards Pete

There's the reason! There's more information and possible fixes described in the User Guide. Please refer to the boxed section under Installation entitled "IMPORTANT: Before updating from 3.71 or earlier to 3.72 or later". (Yes, I know it may not apply to you with that wording -- I'll have to revise that). If none of the remedies work, the only other thing I can think of it to try the Help suggested for signature problems in FSUIPC4 -- see the Announcement above entitled "Help with FSUIPC4 code signature problem". Please let me know how you get on. So far, for Vista, there have been just a few codesigning signature problems, but I need to know what is going on. It looks like something in Vista options can get screwed up. Regards Pete

Yes, of ocurse, assuming you want to use the facilities of FSUIPC and WideFS with both. Yes. Unfortunately you purchased them the wrong way around -- there's a good discount when upgrading to the FSX versions, but not the other way. You only need to back up your FSUIPC.KEY and FSUIPC4.KEY files. You don't need to key them in like a password everytime you want to run FS! Regards Pete

As explained in the User Guide, only the user functions aren't available to an unregistered user. So that program has a problem. Maybe the answer is in the FSUIPC Log file. Please try again, then close FS down and show me the FSUIPC.LOG. It is an ordinary text file in the FS Modules folder, so you can paste it here. Regards Pete

Do you have ESP? Isn't ESP aimed at Corporate customers with integrated solutions supplied by Microsoft Partners, or something similar? I probably have the actual terms wrong, but I don't think a generally available add-in like FSUIPC is directly applicable except as part of such a solution. If you are involved in developing ESP solutions in this way, perhaps you should write to me at petedowson@btconnect.com. Regards Pete

Sounds like you have Explorer set to hide system files. There are three options I always make sure I have set the way which shows me what files REALLY are there. Go to Windows Explorer -- Tools - Folder Options - View: "display the contents of system folders" -- enable "show hidden files and folders" -- enable "hide extensions for known file types" -- disable Regards Pete

It's actually a user problem. ;-) Please read the instructions in the User Guide, and especially note the part (in emboldened red!) about needing to run FSX "As Administrator" when needing to Register. Regards Pete

The last line at least, maybe more. The last line reads something like ***** FSUIPC Log file closed ***** and is a useful indication that all the assorted threads terminated okay and the memory allocations properly freed. If that indeed was the complete log, then it looks as if FSX is not terminating correctly but hanging at the end. Regards Pete

Sorry, no. Pete

In FSX, unlike in FS9 and before, when the ATC Menu is showing it seems to trap the keyboard input itself, and passes very few on at all. This actually seriously clobbers keyboard fliers using ATC, because when the ATC Menu is showing they cannot use the NumPad keys for the aileron, elevator, throttle and trim operations! The problem has been reported to Microsoft but i don't expect it to be changed now before FSX1. Perhaps you should try using the FS ATC controls instead? I've not tried them, but they shouldn't become trapped like key presses would be. See ATC MENU 0 to 9 controls. BTW a full list of FSX controls is installed in your FSX Modules folder by FSUIPC4's installer. In general you are ALWAYS better off assigning the controls directly. Key presses are mainly of use for 3rd party programs. When you send FS a key press it looks it up in its assignments and converts it to the FS Control, so it is always more efficient to assign the control in the first place. ;-) Regards Pete

You still didn't delete the assorted FSX parts set in "Documents and Settings\Application Data", though. I can see that from this in the Log: Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. I can also see the full folder names for the FSX folders you should have removed for a full un-install: C:\Documents and Settings\James\Application Data\Microsoft\FSX\ and C:\Documents and Settings\All Users\Application Data\Microsoft\FSX\ Okay. Yes, if that includes a disk reformat it would certainly get rid of any FSX leftovers! Regards Pete

Thanks for this. I've taken the liberty of putting this suggestion more permanently into the Forum as an Announcement. Best regards Pete

Some folks, especially those with non-English versions of Windows (XP or Vista), are getting this problem with FSX + FSUIPC4: Thanks to a blog by Lefteris Kalamaras begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting ( http://lkalamaras.blogspot.com/2007/06/-good.html ), pointed out by "jammi" in our Forum, this should be quite easily rectified, though it does require Registry editing, so take care. Run REGEDIT (you'll probably have to run it "as administrator" on Vista) and search for the following path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing Then change the value from 0x63c00 (or whatever it has become) to 0x23c00, which I believe is its default (working) value. If none of the above helps, another cause of similar problems has been identified, also in the Registry. Try deleting the following registry key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\SystemCertificates\TrustedPublisher\Safer Regards, Pete Dowson

Oh, good. So, FSUIPC should see it (or them, rather) when you change from one mode to another. It should see one "mode" being released and the next pressed. It is the transition from released state to pressed state which is detected in the options dialogue. Regards Pete

AdvDisplay was discontinued some time ago. It most certainly doesn't work in FSX. The function of AdvDisplay was replaced by facilities in FSUIPC some 2-3 years ago, for FS2004 and FSX. AdvDisplay is only useful now on FS2002 and before. FSX never has a Modules menu. It will have an Add Ons menu if you install FSUIPC4 or other add-ins. Try the Announcements at the top of the forum. That is where all the information is placed, for reference. Posts are ephemeral and so not a good reference point. Look especially at the "List of Supported Versions" where you will find this: AdvDisplay 2.14 (4th November 2005) -- FS2004 compatible No longer being developed even for new versions of FS. The programs which are compatible with FSX are labelled so. Regards Pete

Okay, I have finished streamlining the wind smoothing changes and I think there's no easily measurable performance impact. Version 4.216 is available in the FSX Downloads Announcement, now. Regards Pete