Pete Dowson

But under Vista uninstallers are completely unable to uninstall Side-by-Side instrallations. According to Microsoft, once installed they stay installed (unless you get them out manually as you say). They say it doesn't matter becasue new versions don't have to overwrite old ones, they just sit side-by-side. the problem then is if the re-install tries to install the same (broken) one again -- does it succeed? Judging by what happens on XP, no it doesn't. Version 1.04 of what? 4.072 of FSUIPC? It has nothing to do with any system Log. Sorry, you've lost me now. Were there ever any errors shown in the FSUIPC4 install log? It is at installation time that it checks the installed Simconnect versions, and then again on being loaded -- but I think you said it never got loaded. That "10.0.61234.0" version of Simconnect mentioned in your earlier message is for SP1 Beta3, the first Beta release needing a change in FSUIPC. FSUIPC4.10 can work with the RTM version of SimConnect, or SP1Beta3, SP1Beta4, as well as SP1 RTM. All this is logged. If the system records an error when the Installer or the DLL itself goes through its Manifest Probe loop to find the versions available, that'll just be for information -- the error is returned and the program thereby knows that version isn't installed. Regards Pete

Isn't IVAP a SimConnect client now? They aren't user alternatives. If a program is written to use FSUIPC exclusively, then it will run on WideFS. If it is written to use SimConnect, then it uses SimConnect, and WideFS does not come into it. SimConnect has its own Networking system. No, of course not. It uses SimConnect 100%. How can it be incompatible if it is completely dependent upon it? It sounds like you've added a SimConnect.XML file on the FSX PC which enables the remote SimConnect but excludes the local one. The XML file needs two sections -- a so-called "global" section (confusingly meaning "remote") and the same default "local" section shown in the SDK. If you re-run the FSUIPC4 installer, and the only problem is that you've got a "global" section and no "local" section, it will fix that for you automatically. I have no idea what IVAP does, sorry. Doesn't it come with any documentation or installation guide? Regards Pete

No, none. Everyone has confirmed what I see. When you right-click on the Icon for FSX, there surely must be a "Run as administrator" option? I've now got two Vista installations (one Home Premium, the other Ultimate) and they both provide this option for all programs, not just FSX. I've no idea how to hide ityou must surely have some super-protective settings enabled somewhere, or possibly you are logged on as an ordinary user, not the Administrator? If so, see if there's a "Run as ...." which allows you to specify the Admin username and password prior to running FSX. If you let FSX install in its default place, deep within "Program Files", then you are prevented from changing anything at all in its folders -- it is all part of Vista's super protective system to stop you messing things up. The only way to edit stuff in any Program Files folder is to change access permisions. Please don't ask me how to do that -- it took me several days following other folks' advice and I can't explain it. I eventually managed to make my FSUIPC Installer automatically change access permissions to the modules folder, so I can write the LOG, INI and KEY files there. That was by a lot of "magic" code which I'd find difficult to explain too! I like the *look* of Vista, but pretty much everything else about it does tend to annoy me. Maybe I'll get used to it, one day, but meanwhile I am sticking to XP for development and "real" flying. Regards Pete

You don't need a registered FSUIPC for WideFS, you need WideFS to be registered. However, if they both say "connected" I assume that is what you mean? No idea what is meant by a "missing DLL". Is this for FSC or something you've read to do with WideFS? Sorry, I've no idea what this means. Where are you trying to "open ther client"? The only part always needed is WideClient.EXE. Run that. It sounds like you are running it in any case if it says "connected", otherwise it couldn't say anything! ;-) If you want any help with muy programs, I need these things please: Version numbers: Wideclient and FSUIP4 version numbers. Log files: Wideclient.Log for the client, WideServer.Log from the FSX Modules folder, and FSUIPC4.Log also from the Server. From the rest of your message it seems you have Windows hiding the filetypes like "INI", "TXT" and "LOG". The Log files are text files so if you double-click on them you can read them. Do that then copy them here. Or else change your explorer options so you can see files by their names. Regards Pete

Ah! I didn't know that. So, is the only way to "repair" a broken SimConnect on Vista to uninstall and re-install everything? I think the problem on Vista with that is that uninstalls NEVER remove Side-by-Side installations, so when the re-install occurs it will probably be unable to fix the broken SimConnect! I think I need some more expert advice so I can change my "FSX Help" text properly. Regards Pete

One minor point there: the string should always be zero terminated, so for an "h" on its own you needed 2 characters, 'h' and a zero byte. You were just lucky that the next byte (in 3381) happened to be zero already. The length in the Write to 3380 is still only 1, so only 1 byte is written to 3380. you need the entire string length including the zero at the end. Not surprising when you look at your code. you are writing a charracter to 3380, then overwriting it with the next, etc, til the last. So, the only one left in 3380 is the last. Isn't that obvious? I don't know why you'd want to write only one byte (character) at a time -- it is very inefficient -- but if you do you'd need to increment the offset (3380) each time too, otherwise, isn't it obvious that you are simply writing to the same location (3380) all the time? Why not simply write the whole string at once? FSUIPC_Write($3380, Length(field), @field[a], dwResult); And don't forget to make sure there's a zero byte ending the string and included in the length. Regards Pete

Do you have the documentation from the SDK? There it states: As it implies, the positions and names can't be changed, only the loadings, and then such changes don't have the desired effect -- in FS2004. The facility should work better in FSX as it is officially supported now via SimConnect. FS most certainly doesn't automatically reload anything. There is a "reload user aircraft" control you can assign, however. Have you tried that? Regards Pete

Sorry about thatI'll add something to the ReadMe. Meanwhile here's the details of each of the CSV files: RUNWAYS.CSV (ORIGINAL RUNWAYS FILE -- for FStarRC): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreq* R4.CSV (RUNWAYS FILE for RCV4): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreq*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset* R5.CSV (RUNWAYS FILE for RCV5): ICAO, Rwy*, Latitude*, Longitude*, Altitude*, Heading Mag, Length*, ILSfreqFlags*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset*,Status* G5.CSV (GATES for RCV5): ICAO, GateLetter, GateNumber, Latitude, Longitude, Radius*, HeadingTrue, GateType*, AirlineCodeList ... T5.CSV (TAXIWAYS for RCV5): ICAO,TaxiwayName,Minimum Width*,PointList ... where PointList is a sequence of: Latitude,Longitude,TaxiType*,Width* * Rwy is nnn for runway number, then 0, 1=L, 2=R, 3=C, 4=W (water) * Latitude is of threshold or AFCAD's "runway start" * Longitude is of threshold or AFCAD's "runway start" * Altitude in feet * Length in feet * ILSFreq as nnnnn for nnn.nn, or just 0 when no ILS * ILSFreqFlags is ILSFreq then optional B (backcourse), D (DME) G (Glideslope) equipped * ThresholdOffset in feet * Status: ,CT for Closed for Takeoff and/or ,CL for Closed for Landing * Radius in metres * TaxiType is 0 = unknown 1 = Normal 2 = Hold short 3 = unknown 4 = ILS hold short * GateType is: 0 = none 1 = Ramp GA 2 = Ramp GA Small 3 = Ramp GA Medium 4 = Ramp GA Large 5 = Ramp Cargo 6 = Ramp Military Cargo 7 = Ramp Military Combat 8 = Gate Small 9 = Gate Medium 10 = Gate Large 11 = Dock GA Regards Pete

I don't know a thing about designing aircraft for FS, but I assume it's all part of the graphic design, in the MDL file? Maybe you need to download the aircraft design SDK from the Mcrosoft websites? Regards Pete

No one had ever asked for tis data from FSUIPC before in all its 7 year history, and I've no idea how to find it in FS's innards. The same really goes for most of FS's aircraft design data (whether from the AIRCRAFT.CFG file, or its AIR or MDL files). The main reason for supplying fuel tank capacity and fuel indications is so that external gauges and fuel displays can be made. Unless you are trying to replace the actual flight simulation activities of FS I'm not sure why it should be able to supply any aircraft design values in any case. Surely, in that case, you'd need much more data anyway. Can you explain? Regards Pete

I don't understand the code at all (not my area), but in C/C++ "long" is certainly not usable for receiving a "double" as, even if it doesn't get "converted", a double is 64 bits long and a long is only 32 bits. In C/C++ you'd read 8 bytes from the quoted offsets directly into a double. Regards Pete

Apologies! It was at the end of the line when it was first added and the ReadMe updated, but of course there are other things added after. I'll amend the ReadMe! Pete

Good! No, it won't just by copying in the Modules folder. You have to run the Installer to get the correct parameters into SimConnect's files in your "Documents and Settings". FSX is not like FS2004 -- it won't load DLLs just because they are there! This is why I had to build an Installer for the first time. Sorry, I don't know what that means. But never mind. I'm glad it is all okay now. Go fly! Enjoy! Regards Pete

No! By coincidence, Registry update files (which used to be ".reg" files) came to be called .key files some time around when XP came out I think. But the FSUIPC.KEY file is NOT a registry update. It is simply a text file containing your Key infomation. Do not double click it! If you want to view it, right-click on it and open it with Notepad. Pete

FSUIPC will install in any folder you correctly install FSX into. It doesn't care what the folder is. The problem you had was that the Registry did NOT point correctly to the FSX folder where it should have done. This would cause you problems later. I also said that if you re-installed FSUIPC using the later version of FSUIPC it would offer to fix the registry for you. In order to get the registry pointing to the wrong place, you must have actually moved FSX using Explorer. I always install FS into nice easy folders to remember, like C:\FSX or more usually on a different disk altogether, like E:\FSX. On one system I have FS2002, FS9 and FSX all installed like that. I only let FS install itself in the default places for testing installers. ;-) After you load FSX with FSUIPC installed, there will be an FSUIPC4.LOG file produced in the FSX Modules folder. There always is, you can't stop it if FSUIPC is running. Just close FSX, find the two files, FSUIPC4.LOG and FSUIPC4.KEY in the FSX Modules folder, ZIP them together and send them as I said. Regards Pete

There's nothing I know that'll do that, assuming FSUIPC4 is installed correctly, and you are running as an Administrator. Please ZIP up the FSUIPC4.LOG and FSUIPC4.KEY files and send to petedowson@btconnect.com, and I'll check them here. I'm away from tomorrow for a week, so please do it as soon as possible and I'll get straight onto it. Why are you reinstalling? If FSUIPC4 is installed and it is running well enough for you to get to the Add-Ons/FSUIPC menu, there won't be that much wrong, especially not enough to justify a re-install. But let me see the files first. Regards Pete

By "go to FSUIPC" do you mean go to the Add-Ons menu, and click on FSUIPC? That takes you to FSUIPC options. Only one of the options there is to register FSUIPC. It never asks you to do anything explicitly. Many folks don't register because they have no need of the extra facilities. If it is registered it will say it is registered, if it is not, it will say it is not registered. The rest is up to you. If you mean it is saying you are not registered, and you are clicking on the Register FSUIPC button, then the fact that is shows your name and email means there is an FSUIPC4.KEY file in the FSX Modules folder containing those details. Also, in that file, there will be the Key you registered with before. It sounds like you re-installed Windows, or rolled back to a previous restore point (before you registered). Is that right? You would need to re-register then, certainly, but you can cut-and-apaste the key from the FSUIPC4.KEY file -- it is only a Text file, open it with Notepad or any text editor. Regards Pete

FSUIPC never asks you to register, either. It never asks anything. If something is asking you to register, it most certainly isn't FSUIPC! Please describe exactly this window or whatever which is asking you such a thing. Obviously if it is another program altogether the FSUIPC Key you have will not work! Regards Pete

With the same sort of error? Were you using this AOL software before, and autothumbnail worked? The fact that autothumbnail stopped working in SP1 may simply mean it isn't compatible with some changes between the original version of FSX and SP1. There have been a lot of changes, and compatibility is only guaranteed for those programs which played exactly by the rules. FSUIPC4 had to be changed to work properly because of some intricate arrangements, unpublished links. What connection to the Internet? Nothing to do with FSUIPC or SimConnect makes any connection to the Internet, so that is irrelevant. The connection which is being blocked, or slowed too much (more than 3 seconds I'm told) is between one part of FSX (SimConnect) and another part (FSX.EXE and its constituent modules in the FSX folder). Okay, if you think that rather than a problem with AOL, please report it with all the relevant details, to Microsoft Tech Support, and also send it all to tell_fs@microsoft.com. Regards Pete

Interesting. I didn't know any weather radar outside of Florian Praxmarer's gauges used FSUIPC to get weather. I've no idea why it might not be showing. First thing is to check that FSUIPC4 is loaded and run by FSX okay -- is there an Add-Ons menu entry containing FSUIPC? Then check the FSUIPC4.LOG file (in the FSX Modules folder). Show it here if you like. It should contain no error messages. If all that is okay you could see if my WeatherSet2 program can read the weather okay when FSX + FSUIPC4 is running. You can get that program from the FSX Downloads Announcement above (also the latest interim version of FSUIPC4). The weather facilities in FSUIPC4 actually work better in FSX since SP1 was released than they did before, so if anything you should see an improvement. You might also like to post your question to the aircraft makers. Maybe it is something they've not got working yet? Regards Pete

How did it become unregistered? Did you delete any files? Or did you reinstall Windows? That would do it. Not sure what you mean by that. What does that mean? Sorry. You'll need to be more specific. First, are you using the current version of FSUIPC (4.10, or, better, 4.104 from the FSX Downloads above)? If not, do so. Second, when you install FSUIPC4 it produces a detailed analysis of everything it does. This shows on the screen whilst it is installing, and you can read it, and, if anything goes wrong, save it. The data in that is far more understandable than your explanation is going to be, so how about using it, please? If you install 4.104 and it works there will be an Install log saved in the FSX modules folder. You can read/show that. FSUIPC never asks for a key. I don't understand what you are seeing. Please describe exactly what you are doing. Also, your registration is nothing whatsoever to do with how or where FSX is installed. Please read the Installation instructions in the user documentation. Then, when you are sure it is installed okay, run FSX (you should run as administrator, especially on Vista, as it says), and only when you are actually IN FSX do you get the chance to register. But you are never ever asked for a key. You have to ask to register, in the FSUIPC options. Please please do read the documentation provided, at least the first few sections. Regards Pete

It means that the FSUIPC options screens aren't "hung" in the sense that they aren't processing whatever inputs they can read, live. That can arise if the system refuses to provide any timers, for instance, or the message queue becomes full. It also means that you could do all your calibrating using the older method of assignment in FS and calibrating in FSUIPC, for now anyway. I now need to know more -- what actual devices you have connected, and a copy of your FSUIPC4.INI file. I probably also need some bits of your Registry (because that's where the Direct Input device identiies are stored). But it is rather complicated to work out exactly what. Sorry, but it looks like I will have to look at this further when I get back, a week Thursday. There's no way I'm going to be able to analyse my code enough to specify what information is needed in time for your response to do any good. It would probably be easier (less error prone too) for me to add a load more logging into the appropriate areas of my code to find out why it sees none of your devices. I've not met this before at all, and I've now tried it on two Vista installations with no problems. I'm wondering if it's to do with ownership. When you installed the devices was it as the same user you use to fly FSX? I probably search the Registry looking only in the current user areas. On my systems there's only ever the one user, who's the Administatrator too. But even then there's an "All Users" section , I see. Pete

No idea about C# nor "forms" (what are they?), sorry. Why would it do that? FS has never blocked anything else. It probably doesn't care anything about your program. How? Does this EPICIO program have an FSUIPC interface, or is it your program talking to FSUIPC? Sorry, I thought EPICIO.DLL was simply an interface library for EPICUSB, not a program specific to FS and FSUIPC. The program I produced for EPIC was EPICINFO. Regards Pete

I know that from the Install log you showed. That doesn't prove FSUIPC was loaded and running when you started FSX. It only shows it was installed okay! But that is the Install log, not the FSUIPC4.LOG file I mentioned! The latter tells the story of why you have no Add-Ons menu! Pete

I'm not surprised. No SimConnect add-ons will work if SimConnect cannot talk to FSX. No, I don't think it is anything to do with ports. But possibly that security program is blocking FSX and SimConnect from talking to each other. It really is the only possibility. You need to make sure it allows FSX to use TCP/IP freely. It's exactly the same problem. Should I assume from this that you've NEVER managed to run FSX+SimConnect properly? It is important to know if something has changed, or this is just another one of the many cases of security programs blocking FSX good and proper? If you never had it all working, please visit the FSInsider website for advice. Microsoft did point out these firewall problems last year. Regards Pete