Pete Dowson

For something like PM, which is entirely controllable via FSUIPC offsets that is usually the best way. But your earlier attempt, using KeyPresses, can also work. You have to program the button on the Server to use the FSUIPC "KeySend" control, with an ID number (1-255) as the parameter. Then you program that KeySend number in the WideClient.INI file, on the Clinet, to send whatever keypress you want. If the programs on the Client are started via Run parameters in the INI you can precisely direct the keypress to the correct program. Regards Pete

No, not a problem. So, what's the current state? With COM50 and COM51? Where's the WideClient.Log file I keep asking to see? Is there still a problem to resolve? Regards Pete

Since, as it clearly says, it isn't used, it matters not at all whether you put it in, take it out, or set it to read "mickey mouse". That's why it says "not used". The speed is irrelevant on the Network link. Okay. And the program you are using accepts "COM51" and speed 9600 okay? Most programs I've used seem to be limited to COM1 to COM9. Sorry, but it is only a freebie which I originally wrote for my own use for a REAL COM port link. Use it that way with a null modem cable if you feel so bad about it. And MixW is not mine at all. There are easier programs to use, but you'll pay $1000 or more for them. MixW is okay for free. Pete

Goodseems that Microsoft, in their infinite wisdom, have forgotten to include the GlobalSign root certificate in their default Vista64 installation, at least in your language version. I'd be grateful if you'd kindly report this to Microsoft Vista support. Meanwhile I'll look at including the fix in the Installer and maybe running it automatically. Regards Pete

I just realised where I'd seen this before. You previously posted in the Announcement about Signature problemsI answered there, and asked you to check the signature manually, and you never replied! That was a long time ago! Here was my reply which you ignored: I don't think messing with that area will help and is likely to cause more harm than good. You surely didn't purchase them before making sure that FSUIPC was working on your system? I don't know. Does the signature check out on the DLL (right-click and check it via Properties)? Pete Seems I have to repeat myself a lot? One other thing you can try. This is actually a remedy for a missing GlobalSign root certificate in early WinXP (pre-SP1) and Win98 installations, but maybe, just maybe, the data has gone missing in your Vista64: Extract the 'GlobalSign Root' program from the following ZIP and execute it on your PC. It will try to fix the problem by updating the Root certificate in your installation. This is an official fix, supplied by GlobalSign. http://fsuipc.simflight.com/beta/Fix_Gln_Root.zip Regards Pete

Where can i find this log :?: In the FSX Modules folder. It is produced whenever FSUIPC4 is actually run. If there is none there, then FSUIPC4 has never been run. Exactly -- this is precisely my point, and why your suggestion, to manually copy the DLL into the Modules folder, makes no sense -- after all it is already there, yet does not get loaded by FSX. Why do you think your manual copying will be better? I'm not sure about all this business of "adding certificates". No such fiddling about should be necessary. Have you actually tried manually checking the signature, as I have suggested before and, I think, explicitly suggested in the documentation? If so, what was the result? I try to make suggestions to help. I am not insinuating anything. I am wondering what you are trying to say here? I am trying my best to help, can you not see that? But something is most certainly wrong with your Vista installation, and I don't know how to fix it. I suspect we'll end up having to get you to call Microsoft tech support. Please see my previous post which I think must have crossed with your post. I have to go to bed now. It is nearly 2am and I can't do any more tonight. Regards Pete

Just to prove this one way or the other, please try this revised version of the 4.26 installer: http://fsuipc.simflight.com/beta/Instalevised.zip In this I have moved the signature check so that it is performed AFTER the correct files are updated and permissions set, and it should also allow you to Register. However, if the signature fails it will tell you, and I think you will not get FSUIPC4 loading into FSX because of it. Please show me the FSUIPC4.LOG file you get in the Modules folder if, indeed, it does get loaded. And please tell me the result of your manual signature check (via the file properties). Incidentally, the Installer itself is also codesigned. Please do a file properties check on that too and let me know. Regards Pete

Erthat's one port of a pair. What is the other? What have you entered into the program which is supposed to be receiving the GPS data? Sorry, I don't understand the relevance of this? The speed parameter isn't relevant in the Server, that's all. But it is in the client of course, and needs to match whatever speed you set in the receiving program. Can you not find the WideClient.Log file? It will be with the WideClient program, next to the WideClient.INI file, not on the Server. Regards Pete

No, your log, as posted earlier, shows that the installer is working fine up to the point where the signature check on the installed DLL fails: Did you check the signature on the DLL manually, yourself? (Right-click on it, select Properties then the Digital Signatures tab). Why have you come to this "conclusion" that the Installer is to blame? The only reason there is an Installer for FSX (I don't like installers and never had one before) is that there is no "modules" folder in FSX until I create one, and just creating one and inserting FSUIPC4.DLL into it does not make it run at all. Files have to be created or checked and edited elsewhere too. The installer has the privileges needed to create the folder, and then it copies the DLL in --the install log shows it has already done this, so how would you doing exactly the same thing manually help? The DLL is the DLL is the DLL. Whether it gets into the folder from the Installer ort by your hand doesn't affect anything at all. The only possible thing I can see that I could do is move the Signature check to a later part of the Installation process, so that the other files get edited before the failure. But as far as I can see, all this would accomplish is to get FSUIPC rejected by SimConnect whjen you tried to run FSX, because of the signature problem. Activation isn't the problem here. The signature check applied by the Installer is just an aid to you, to show a problem which will occur with your FSUIPC installation when you run FSX. Or are you saying that you can run FSX and have FSUIPC running properly, that it is only registration which is your problem? If you can run FSX with FSUIPC4 installed, please show me the FSUIPC4.LOG. Note there are very good reasons why I moved registration to the Installer. There are much bigger problems activating FSUIPC registrations from within FSX than from within an Installer, because an Installer automatically already has elevated administrator privileges. If things won't work in the Installer, they most certainly have no chance whatsoever of working in FSX. Incidentally, earlier you said: Surely you tried FSUIPC4 in FSX on your system before purchasing it? I know you cannot "try" WideFS beforehand, but FSUIPC4 can be used (and is used, a lot) without registration. Regards Pete

My new PC, which I am hoping to receive soon, will have Vista64 pre-installed, so I will certainly be able to test things then. However, there have been a number of reports from Vista64 users with no such problems at all. Do you think it is something in the Vista Servce update (SP1?)? Pete

COM 50 isn't right -- there most certainly should be no space, so possibly COM50 would be correct, but 50 seems an awfully big number for a COM port. Normally MixW uses the next pair of COM port numbers available -- have you already got 49? What is the other number of the pair, the one you've set in the program to receive data? Where did you get '50' from? Where's the WideClient log? Pete

Okaybut you can also send FS controls via offsets, see offset 3110. As you will see there are several ways of doing things. If you are writing direct to the time offsets, you might find you need to write the ZULU time rather than local, of maybe both. You'll need to experiment. Try things with FSInterrogate. Regards Pete

Yes, your Name and Email are you "ID" for registration purposes, and you cannot have FSUIPC and WideFS simultaneously registered to two different people (two IDs). It does say this in the User Guide. SimMarket can fix this for you, or else you can send all the details to me: I need your FSUIPC registration details -- name, email, key) and your new WideFS details (name, email, key). Send to petedowson@btconnect.com. Tell me which ID (name, email) you want to use. Regards Pete

You can obviously use Offset Byte Set to write any value you like, or use the offset INC or DEC controls to add or subtract 1, but 0238 is only the Local hour. What about minutes? Why make is so complicated using FSUIPC offsets anyway? FS has controls for this - CLOCK HOURS DEC, CLOCK HOURS INC, CLOCK MINUTES INC, CLOCK MINUTES DEC, CLOCK SECONDS ZERO, as well as ZULU HOURS SET, ZULU MINUTES SET ("SET" controls" need the parameter for the value). Some of these may even be assignable in FS's own assignments dialogue. Have you looked? Regards Pete

Okay. I received the files and managed to reproduce the crash. It is a localised weather data structure from FS which contains a NULL pointer where the current visibility should be. It seems to do this because the visibility is unlimited, but I've never seen it set NULL before -- it has always had a pointer to the value which indicates unlimited. This is in a part of FSUIPC dealing with the weather reading which has remained pretty much unchanged since FS2000 days (i.e. over 9 years ago), and yours is the first occasion I've been told about which crashes! Amazing! Anyway, it is certainly my fault, as the possibility of a NULL pointer should have been checked. Please download version 3.801 using this link: http://fsuipc.simflight.com/beta/FSUIPC3801.zip and the problem should be fixed. Just put the revised FSUIPC.DLL into your FS2002 Modules folder. Regards Pete

Is GPSout set to use WideFS? Is the WideClient in the client PC set to receive GPSout data? If you enable all of them at once you may need to make the frequency much more than the default 1 second or whatever it is, depending on the port speed you've set in the client and in your receiving program. Sorry, I don't know that program either. But it won't be a "port from another computer", it will be one of the pair of virtual COM ports you created with MixW. I've no idea what "courseplanner" is, but sharing files across a network is not a function of any of my software. You need to sort that out in Windows networking. WideClient on the Client PC will log the data if you ask it to. Set the Log parameter in the INI to read "Log=PartRX". It will log other stuff too. Regards Pete

You'll need to find out how to make them work like FSInn does then, or get FSInn to improve their weather settings. I really don't know how to help further. Maybe, if all FSInn is doing is setting global weather, no local weather stations at all, the older, FS2002 versions of FSMeteo or ActiveSky (before they were changed to set localised weather stations) will do what you want better. However, I still don't believe global weather can be sustained in FS2002 for long unless it is continually reset (cleared and reinstated). I don't know how FSInn does that without you noticing. Regards Pete

So, you stated the condition yourself: have them light up when the value is NOT 1? i.e. L1=X5624 U8!=1 L2=X5625 U8!=1 You only need separate Conditions defined when you want to combine things. You don't want any combinations here, surely? A mask is a patten of bits "masking" or identifying the bits you need. Bit 4 is the 5th bit up, i.e. in binary in a Byte it is 00010000. The hex value is therefore x10 (4 bits in each hex digit) and decimal bit 4 is 2^4 = 2 x 2 x 2 x 2 = 16. For 2 bits, say 4 and 5, you simply add them. 00110000 = x30 = 16 + 32 = 48. Pete

Okay. Sounds like they use the FS weather download facility. Why do you want to use ActiveSky or FSMeteo instead when you get what you want already with FSInn? Regards, Pete

Yes. That makes sense because I think WidevieW struggles to get the weather identical in each copy of FS9 -- the problem arises because FS9 weather is dynamic, and localised, even when set globally. I think WidevieW should be able to do a better job on FSX where the global weather can be enforced -- but then there are other problems on FSX, like less control over cloud types and thickness. Is FSInn feeding every PC, like having several copies of ActiveSky? No idea. I don't know what FSInn is doing. Sorry. This is really not related to any program of mine, except insofar as the weather data being passed to FS9 via FSUIPC. Does FSInn do something of its own, not using FSUIPC? Regards Pete

No, nothing. You shouldn't get a crash no matter what. When you do the re-run to get the Logging files, at a point before you get the crash, could you please Save a Flight (press ; and give it a name). Include the resulting FLT + WX files with the logs, and tell me how to proceed from that point to get to the crash. If I can reproduce the problem it will be much easier for me to work out what is happening -- I think I still have an FS2002 around here somewhere. ;-) Regards Pete

It should also have found the SP1 SimConnect build, but didn't. As shown in the FSUIPC log file, I did build in code to try to recover from this -- if the first version of SimConnect I try returns an error, I try backtracking to an earlier version. However, it seems that when SimConnect is mis-installed it cannot do this. I advise you to uninstall SP2 (or Acceleration if that is what you tried, and then install SP1 first, then SP2. If you are using Acceleration you should be able to get away with only re-installing Acceleration, as it is supposed to include SP1 too. Regards Pete

Actually, please amend that -- enable Weather logging too, please. I've just checked, and that offset is in the weather reading part of FSUIPC. I'm wondering now if it might be a corrupted weather file. Are you always starting with the same weather? Where is the weather coming from? Does it happen if you clear all weather first? Regards Pete

Well, I don't get urges like that, but it is easy enough to do so it'll be in the next update. I can't say when that'll be though. Watch the FSX Downloads announcement. Regards Pete

Sorry, I cannot support 3.75 therefore it should not be supplied. I've contacted HiFiSim and apparently they seem to have made an error, and check explicitly for 3.75 or else refuse to connect! I think they should be issuing a correction quite quickly. Regards Pete