Pete Dowson

What is Symantec's Redirector supposed to do? Is that part of the complete Norton SystemWorks installation? I used to use SystemWorks until I changed to Windows XP -- I was 100% Win98SE for quite a while, only forced over to XP because Matrox don't support Win98 for the Parhelia. Since changing to XP (almost 2 years ago now) I had loads of odd problems with bits of Norton or Symantec stuff, but I don't remember the details I'm afraid. I uninstalled it all and just installed the separate free-standing Anti-Virus package (NAV). Anyway, I hope you really have isolated the problem. Regards, Pete

My programs don't explicitly use any Windows services that I'm aware of, but I suppose some are needed for basic things like linking to other PCs on the Network. Well, I hope you do get a list together -- it would be useful to anyone seeking maximum efficiency, especially under Windows XP which seems to have far too much going on all the time. If you do find a list or get one put together, please post it somewhere nearby and let us know. Regards, Pete

Eryou are of course seeing the INI file -- you have Windows set in the mode where it hides the filenames from you and guesses the file functions. How do you think you have two file with the same name ("FSUIPC")? This is actually impossible! "INI" and "CFG" files are both considered to be "configuration settings" files by Windows, and "LOG" files are considered to be text files. Pete

FSUIPC provides the UNC path if it can obtain it, otherwise (if it is not shared), it provides the local path. This is not optional. here is the definition of the offset I assume PM is using: If you check the FSUIPC LOG file you will find the path determined by FSUIPC and placed in the offset, logged as follows (this is from my PC). I'll show the context, a list of things shown initially: 11297 System time = 17:12:10 11297 \\NEWLEFT\N\FS9\ 11297 System time = 17:12:10, FS2004 time = 12:00:00 (00:00Z) 20641 I:\My Documents\Flight Simulator Files\737 at Seattle.flt 20766 AIRCRAFT\b737_400\Boeing737-400.air 20766 Aircraft="Boeing 737-400" The line "11297 \\NEWLEFT\N\FS9" gives the path, and here, as you can see, it is a UNC one. Check this on your system. It it is not showing a UNC path it is because FSUIPC cannot derive this, and as far as I know the only possible reason for that is that it isn't shared. Regards, Pete

There's normally no need to be sorry. What for? Have you solved the problem(s)? Regards, Pete

It is generated when you first run FS with FSUIPC correctly installed. Three files are created, all in the FS Modules folder -- FSUIPC.KEY, FSUIPC.INI, and FSUIPC.LOG. (You would have been better off keeping these when reinstalling FS). If those files are not being created, then FSUIPC is not running, which means it is not installed. To install FSUIPC copy the FSUIPC.DLL file into the FS Modules folder, as described in the User Guide. Pete

Don't check it there. Load up FS, get to the FSUIPC options (Modules menu, FSUIPC, or ALT M F) and see what it says on the first page. In Windows Display properties. Please do refer to the FSUIPC User Guide. I explicitly tell you in the documentation for the "stop cockpit sizing .." option how to turn that off. I shouldn't need to copy bits of the documentation into messages like this. :( Regards, Pete

"mo" being a "moment", or a "month"? If a month, then it wouldn't have been version 3.30 back then -- but I'm glad to see you are keeping up to date. When you re-installed did you delete or lose your FSUIPC INI and KEY files? If so you would need to re-register, and then re-establish all your option settings. The cockpit moving option can only work if you switch off the Windows option to see windows whilst they are being dragged. I think this was defaulted off in Win98 but on in WinXP -- please check the FSUIPC user guide for full details. On the other one, how are you detecting that the option to prevent programs changing some controls is not working? I think there are only a couple of programs which try to change some of the options in any case -- FSMeteo, being one of them. If you give me more details of what you are seeing I can advise better. Regards, Pete

Sorry, I thought I'd given you three possible solutions too? If you want an accurate heading, with fractional part, you have to use floating point -- fixed point integers do not include fractions. I don't know what you want to use the result for. If you only want the nearest whole degree then the slight modifications to your formula which I showed you will do the trick. They just force the calculations to be performed in an order designed to keep the intermediate results within the 32-bit capacity of the "hdg" variable. Regards, Pete

Ouch. With WinXP there's nothing t normal application program level that can do that. It must be a low level problem. Viruses are the first suspect, as there are certainly some which do this deliberately, but I see you've checked for those.. The only other problems I've ever had which do similar things are overheating (I still do with one PC in the Summer unless I leave its side cover off), and faulty RAM (fixed by removing one chip at a time, then replacing the one which when removed fixed the problem). But I suppose other things like a faulty card, hairline crack on a motherboard, faulty drivers, etc etc could all do the same sort of thing. Either you are loading more stuff into the PC then, so it is working harder or using more RAM, or it may be a problem with the Network card or driver. Try uninstalling it and re-installing it. If it's a separate board (i.e. not on the mobo) try swapping it with another. If it is on the mobo, try disabling it and adding a cheap netwrok card instead. Ahthe non-FS PC is a notebook? That makes it a bit more difficult to play around with changes to eliminate things then. Try uninstalling and reinstalling the network card anyway, but in the end you might need to get the machine checked over by a specialist. Regards, Pete

Hey? I like "Hi" better, "hey" is a bit like shouting isn't it? Is the "it", which is telling you, FSUIPC or Squawkbox? If FSUIPC then you are getting it wrong, somewhere -- this only happens if the Key itself is invalid or of the wrong type. If you can give more details I should be able to help. Always quote version number of FSUIPC, and tell me what you are trying to enter and where. Regards, Pete

That's getting pretty old now. Please try to keep up to date. Current is 3.30. What is "hdg" defined as? If it is correctly declared as a 32-bit unsigned integer (i.e. a DWORD in Windows terms), then there are two errors here: 1. Multiplying it by 360 will probably make the value too large to fit -- after all, the scaling in FS is deliberately designed to make the largest possible value (just under 360) fit exactly into those 32 bits (ie. as 0xFFFFFFFF or exactly 65536*65536-1. Think about what happens when you multiply the biggest possible number by 360. 2. Dividing a 32-bit value by 65536*65536, which is one more than the biggest number that will fit into 32 bits, will give zero, if it works at all. You need to copy the value you read into something bigger for this to work -- either a 64 bit integer (if you don't care about fractions of a degree), or, better, a floating point number (then you get fractions too). If all you want it the nearest degree you could do it something like this: hdg = (((hdg + 32768) / 65536) * 360) / 65536; This way you keep the value within the 32-bit capacity of "hdg" at each stage. I've added 32768 to start with to round up the fractional part if it is .5 or above. However, this may give you 360 instead of 0 from a value like 359.5 or above, so you also need to do this: if (hdg >= 360) hdg = hdg - 360; In programming you need to always be aware of the data types you are dealing with. Arithmetic on computer variables isn't just a matter of writing the formulae down. Regards, Pete

Sorry, I've not heard of "the ProMFD fuel page". Is that an add-on package? Isn't this question best directed to its author? Regards, Pete

Strange! There's no such new logic! The driver has ALWAYS supported any speed. It simply defaults to 9600. Nothing in any of that has changed in two years! Furthermore, because it is defaulted it isn't needed in the INI, as you've found out. I honestly don't know what happened in your case, but simply changing from 1.8xx to 1.90 couldn't have been responsible. The internal value is predefined, as a constant, as 9600. If there is no parameter provided, that is undisturbed. There's no simpler logic, and making the parameter explicit won't change a thing. Regards, Pete

Isn't that the point of "observer mode" or whatever it is called, in multiplayer? Sorry, I've never really used multiplayer at all since about FS2000, and then only out of curiosity, but I thought you could do exactly that. No. you misunderstand WideFS. It is to link FSUIPC client applications running in a PC not running FS to a PC running FS. In other words it is a Networked FSUIPC interface. Regards, Pete

No, it looks like either a bug in Windows, or in the video driver, or possibly you have some additional software running which does fancy things with some windows standard tools? The size of the fonts shouldn't matter as the sizes of dialogues are specified in units related to font sizes, and Windows libraries actually rescales everything to match both screen resolution and fonts. Please check that you have all the Windows updates you should and that you are not running somthing that plays with these things. If you need more advice I think Katy Pluta, over in the FS2004 Forum, will be able to help. Regards, Pete

Sorry, no. Let me know if you come across anything! Regards, Pete

Because the plan doesn't get as far as KLKV. Check it yourself. The last place it gets to is LMT. Also the plan you sent (the fcf file) is different to the PLN -- looks like you changed it or sent the wrong files. The PLN goes via KAGYE (?) not LMT. Either way, you certainly need to have both departure and arrival airports in the plan. Pete

Yes, of course. You think I didn't think of that? :roll: You are very welcome to try to work the format out. When you have it all well decoded and documented please let me know. Regards, Pete

FSUIPC has absolutely nothing whatsoever to do with multiplayer. You've got something else going on there. Regards, Pete

It certainly works okay with 8.5. Why weird? I can't get at the Jeppesen plans or data directly because it is encoded. I have two possibilities, one is trying to decode the graphics in the window when the flight plan is displayed (optical character recognition? Ugh!), or getting the data sent to the printer and intercepting it on the way. How would you do it then? Anyway, it isn't the printing of the "flight plan" (how do you do that?), but the Navigation Log-- the DOC is quite explicit. It says this: Not even the INI file? As the DOC says Well, you have a faulty FliteStar then, as those functions are nothing to do with FStarRC, but used by FliteStar to save the plans in its own formet. You need to report this to Jeppesen, because it isn't much use if you can save the plans, unless you always intend to fly new ones? Get back to me after you get FliteStar itself working correctly, if you still can't use FStarRC, but please be much more specific about exactly what you are doing. Vague terms like "print the plan" aren't sufficient, sorry. Regards, Pete

Not arrived yet though. I'll check again later. Pete

Hmm. As documented, you have to take care to use the same details for both. SimMarket will re-issue one or the other on request, but it might be easier to send the stuff to me. Send me both your orginal FSUIPC notification of Key email, and your WideFS one, and remind me which you want to prevail. Send to petedowson@btconnect.com. Regards, Pete

What problem? The thread subject is only "OOPS", rather unhelpfully. Why not keep to the thread mentioning it, if there is one? I can't even find a recent thread by "Cubby". Maybe you posted to the wrong forum? Regards, Pete

If the CH device is capable of sending multiple button values at the same time, yes. You use conditional programming, with flags for latching states if you like. But it isn't user-friendly. you have to do it by editing the FSUIPC.INI file. Everything you need to know is described in the Advanced User's Guide. Game port CH devices used a system of encoding each of up to 15 buttons into the 4 button lines on the game port. with those you cannot use a button for a shift whilst pushing another, as the state reflects only one of them at any time. With that type of connection you would have to use the flags in FSUIPC to latch different states according to the presses of your chosen selector button. Regards, Pete