Pete Dowson

There's was no access checking before version 3. It won't work. The first version of FSUIPC which works with FS2004 was 3.00. .But this is only because Squawkbox is not being allowed access to FSUIPC, and that is only because the name of the porgram, as it is being run, is not right. Just run it as Squawkbox, and make sure it has the correct Access Key entered, and it should work fine. I really don't know where you are getting those strange abbreviated names from. Regards, Pete

I suspect that the traffic files you are using were tuned to FS2002. The AI airspeeds and so on have been corrected in FS2004, and that and other changes will probably throw some such carefully timetabled operations into disarray. I'm waiting for the FS2004 edition of Ultimate Traffic, which I understand is currently in Beta. Regards, Pete

I think this one should certainly be fine with the access key correctly entered. Check the FSUIPC.KEY file. Does it have the Squawkbox entry listed? If you are getting the "not accredited" message then it simply means the access key hasn't been entered. You don't need to keep downloading FSUIPC and re-reading some readme, that won't really help. Let me see the [Programs] section from the FSUIPC.KEY file, please. For example, if you entered it as "Squakbox" it won't work. Regards, Pete

I've no idea. What do you actually type into Start-Run? "Squawkbox"? Is the program actually named "SquawkBox.exe" in its folder? Maybe it is actually named with the DOS shortcut -- maybe the folder as well? The folder name doesn't matter much to FSUIPC, but the program name is critical. If it is misnamed please just try renaming it to "SquawkBox.exe" (right click it, select Rename, and edit the name). Possibly some installer or unzipper used the DOS abbreviations? Maybe a very old DOS or Windows unzipper? It's described in the Advanced Users guide, but there's an easy way -- download Jose's "Run Options" program from http://www.schiratti.com/dowson. that does it for you. But it still won't work if the name is wrong. Check that first, and rename it to its correct name if it is wrong. Regards, Pete

There are two separate buttons, one for FSUIPC and the other for WideFS. The one for FSUIPC will be greyed out, the other will still be available if you've not yet registered WideFS. It too will grey out when you register. Check the labelling on the buttons. The other thing to be aware of is that the Name and Email must be identical in both cases -- those will be greyed out. If you bought both keys at the same time this will be no probkem in any case. Regards, Pete

There's no "-" characters in the Key, but it wouldn't have taken those in any case. The correct name according to the list published in the Forum is "SquawkBox". The capital B may be important (I'm not sure -- but it is always best to be accurate). The real problem is this: 78391 Client Application: "SQUAWK~1" (Id=2092) 78391 F:\FS2004\ADDONP~1\SQUAWK~1\SQUAWK~1.EXE 78391 Product="SquawkBox 2.3" 78391 Company="None" 78391Program not accredited for use with this unregistered FSUIPC The program actually running is appearing as "SQUAWK~1" not as SquawkBox, so the key will never match. How are you running the SquawkBox program? That sort of name is a DOS type 8-character abbreviation for it. In fact the whole path is a DOS abbreviated path: F:\FS2004\ADDONP~1\SQUAWK~1\SQUAWK~1.EXE Surely you are not running this from a DOS batch file or similar? What operating system are you using? It seems very odd to see this sort of abbreviation these days, and certainly none of the Keys will work with an abbreviated program name. Try using RunOptions and getting FSUIPC to load it for you, using its real name and path. BTW the log also shows you are not running an accredited version of Whazzup: 80485 Client Application: "WhazzUp" (Id=3076) 80485 F:\FS2004\ADDONP~1\WhazzUp\WhazzUp.exe 80485 Product="WhazzUp" 80485 Company="Enrico Schiratti" 80485Program not accredited for use with this unregistered FSUIPC You need to check with the Project Magenta site for an update with a correct access key. Regards, Pete

Yes, of course. Please write to me at petedowson@btconnect.com and I'll send the details. Regards, Pete

No, certainly not. I mean that the code may not be correct for that copy of Squawkbox. That's why I said to check the FSUIPC log after you've run SB. Also to double-check the Key you are entering and the SB exe's details against those in the list above. Pete

Yes, but a "legal" code is not the same one as a correct code for that program. The check is only on the basic integrity of the Key. The actual check needs not only the program EXE name, as entered, but also details from the program's Version Information, which is not known until you run the program. Please check these details against those in the Free Keys list earlier in this Forum. Regards, Pete

I've only just discovered this today -- it is in FS2002 or before only. I've said this in the "Important" announcement. I wil fix it within the next couple of days and provide 3.08 when I can. Sorry. Unfortunately the original report was for FS2004, so a couple of days or so were wasted on this looking in the wrong places. Never mind. It will be fixed. Regards, Pete

Right, I can reproduce this only in FS2002, not FS2004 (== FS9) as you have indicated. I'll work on a fix for FS2002 and release it later this week. If you do also get it in FS2004 I will need to investigate further, because I cannot see how it can go wrong now in FS2004. Regards, Pete

No. Maybe there are other SB users who can help. But please, also check for me your FSUIPC.LOG file. Does it show Squawkbox connecting at all? Can you show me it? Pete

Have you entered the access code for Squawkbox 2.3 into FSUIPC's program registration dialogue? Check your FSUIPC.KEY file. If Squawkbox isn't listed there, then you haven't registered it so it has no access. The free registration code is in the list in one of the messages near the top of this Forum. As for Whazzup, it has got an accreditation code to allow it to access FSUIPC, but I don't know if that is built in or not, nor what version. You'd need to check with Project Magenta support. Neither of these things is needed for user registered copies of FSUIPC, but otherwise you need to register freeware programs if they don't do it themselves, and make sure you have the correct FS2004-ready versions of others. Regards, Pete

Not seen thatI hardly ever see any planes, and I've got it at 100% Tell me how to do it, please! I'd like to see that! And, no, sorry, there's nothing in FSUIPC to influence AI habits. I don't think you can without recompiling the Traffic files -- although there may be a way to delete AI aircraft, which I might provide an interface to one day. Regards, Pete

Yes, I found the bugAutoSave 1.48 isn't keeping its CFG file up to date as it writes new files. This is a result of the way I find the correct path on non-English versions of FS. :oops: I've fixed it here and I'm just giving it a thorough re-test before releasing it as 1.49, later today or possibly tomorrow. Very sorry. It seems I am getting careless in my old age. I will have to consider retiring from all this soon! :? Regards, Pete

Sorry, please contact him directly with this. There is absolutely no change in any of the weather facilities in FSUIPC for FS2002, none at all. The changes must all be in WeatherCentre. Actually, didn't someone say Damian of ActiveWeather had taken this program over now in any case, or am I mixing up some other weather programs? Regards, Pete

[quote name="Foxgolfbravo Sorry' date=' Pete i use already 1.48 version released on the 8th Sept. There was a probleme with the FS title bar (maybe remembers you, I had sent you some screens shot to this subject) which is fixed, but always this quantity of files beyond 10... Any idea? [/quote] No, none at all. I was sure that was fixed, as the only reason which could be for that is that it cannot find the folder. The folder is certainly named by one of the strings in LANGUAGE.DLL. and that is what AutoSave (and FSUIPC) now uses. Perhaps you could Zip yours and send it to petedowson@btconnect.com? It's in the FS2004 main folder. Thanks. Pete

Yes, I know. I made changes specifically for the French version and it was tested for me, a week ago. Please download the latest version (1.48, released on the 8th September) with all those changes in -- it now gets the final folder from FS's own Language.DLL, which is where FS itself gets it from. Regards, Pete

Can you send me an email on petedowson@btconnect.com so I can send you a Beta FSUIPC as an attachment. I need to get more information. I have changed it so that it does the same as 3.06 did, so it shouldn't muck anything up (but keep 3.06 just in case), but also logs some extra information for me, so I can understand why the 3.07 mod failed on your system -- I've stared and stared at it (only two lines of code) and I just don't understand how 3.06 could work and that 3.07 change not. I would understand it better the other way! Thanks! Pete

Ouch! :cry: There is a change in 3.07 which was designed to fix a problem on one users system whereby the Joysticks tab didn't appear. I believe the same problem would have prevented the FS controls from being assigned too. This change did make this all work on that user's system, and as far as I can see should not actually mess anything up on any other users system either. Evidently I was wrong. I don't understand this at present. It works on the original problem system, and it works on the three different systems I have tested it on hereso it is a puzzle. I will get back to you on this when I have some more ideas. Sorry for the inconvenience. Regards, Pete

The post in "Important" about black screen problems has been there for some time. I only updated it on release of 3.07. When you say it wouldn't go into full screen at all, do you mean you've never run it in full screen mode? If so it is more likely that there's something wrong with the Options - Settings - Display Hardware options. Not necessarily. Only if you want to retain whatever options you liked in FS2002. Some won't apply in any case, but things like keyboard and button assignments, joystick calibrations, some of the hot keys, and so on, will apply, if you used those and you want them to operate similarly in FS2004. The INI file is just where all the options in FSUIPC's dialogues are remembered, that's all. Regards, Pete

When you rename it, do you rename it to "FSUPIC" as you keep calling it, or what? The correct name is "FSUIPC.DLL" and it needs to run with that name. Are there FSUIPC.INI and FSUIPC.LOG files in the Modules folder? Can I see them if so? Your problem is very strange, I've had no other such report. But I need to know more. I don't like the sound of this "renaming" business. what is that all about? Regards, Pete

All I did was link the offset 3BA0 to the position of the "double" which seems to be called "Tailhook position" in the SIM1 data. Maybe it isn't a double after all? Did you see what it meant as an int (DWORD)? Did you try it in FS2004 or FS2002? If one, try the other too. I've no idea what I'm doing with such values. I don't know how to operate it, nor to tell if it is working or not. All I can do is follow clues in the code. And that takes many hours of tracing through disassemblies. It might have helped if I could have seen it changing, but every aircraft I tried only ever had 0.0 in there. And, sorry, but there's no way I can determine more before Monday. If that isn't the right place it could be a week's solid work trying to retrace through the code, assuming I could start with something I knew did something to it. :cry: Regards Pete

Most if not all menu options presumably set something somewhere inside FS which may, if changed directly, have the same effect as using the menu items. However, I'm afriad I really don't know where they are. I did manage to find the one affecting dynamic weather changes, but I couldn't find any of the others in the ordinary weather menu. In any case, judging by my findings in FS2004's Weather DLL, it is more likely to be a lot more complicated. In FS2000 and FS2002 I could find where to write something to change stuff like winds, pressure, and so on, just by changing data. In FS2004 there's no way I can see to do that. It's all procedural -- I can change data and it no effect whatsoever. After changing the data several functions have to be called with the right parameters to make it effective. Even just to clear the weather, which used to be one call, is now three calls. Why? I don't know. I only found out how to do the few things I do by tracing through the code, watching what it did, then by trial and error trying to do the same till I hit on the right combination or sequence. The part you mentioned is actually to do more with graphics settings than weather generation, and I don't know where any of those are at all. I know that Lago's top programmer did master many graphics things in FS2000 (hence "FSAssist"), but I never got very far with any of that stuff. And that was with FS98/2000 when things were a lot simpler. As more and more of FS has been re-coded in C++ with a load of object oriented "black boxes" it's been getting harder and harder. Regards, Pete

In that case Windows will not stop you deleting the DLL unless you had deliberately protected it -- e.g. made it read-only. It sounds as if you made a small error somewhere trying to delete it. All you need to to it select it in Windows Explorer and press the delete button, then Ok for for it to go into your recycle bin. I don't know, sorry. Maybe. I only suggested that as a possibility because, as I said, there is nothing in FSUIPC which deals with views nor which, by default, makes key assignments. And in an unregistered copy of FSUIPC there are no key assignments possible in any case. Once you register FSUIPC you have access to all the options. If you still have your FSUIPC.INI file from version 2.xxx then the options set in that will apply if you copy it into the modules folder (before loading FS, of course). Regards, Pete