elsmoko

Hi Pete, I've uploaded this issue to a few other places; but hoping you can help. I'm not able to tune most VOR/DME stations in United Arab Emirates (Dubai, etc.) . No problems tuning stations near Seattle. Have tried default and payware aircraft with same results. Non Tunable stations : DXB 108.4 MIN 115.2 JXB 113.4 ADV 114.25 ALB 114.0 MA 114.9 FJV 113.8 Tunable stations: RAV 113.6 SIR 113.75 Is this a known issue with (perhaps) a solution? If no, I'd appreciate any tips / suggestions you may have regarding troubleshooting and / or a fix. Best regards, Ken Boardman

Installing VAFS5 on the primary (FSX) PC and then running the airport DB update yields the same results ~:) Stealth virus ha, ha I'll keep you in the loop Pete. Thanks again, Ken

Hi Pete, Thank you for the suggestion. Setting the makerwys file to Read Only caused VAFS5 to yield an error message in the VAFS5 log file when I tried to update it's DB via WideFS (excerpt below). Haven't received a reply as yet to the message I submitted about this to the VAFinancials forum. I'll let you know when / what I hear from them. Best regards, Ken [iNFO ] 2012-09-23 11:31:56 - Starting VAFS [iNFO ] 2012-09-23 11:31:58 - VAFS Initialization Complete. [iNFO ] 2012-09-23 11:31:59 - Login Button Clicked. [iNFO ] 2012-09-23 11:32:02 - Starting FSUIPC Comm Timer [iNFO ] 2012-09-23 11:32:07 - VAFS Options Button Clicked. [ERROR] 2012-09-23 11:32:14 - Runway Database Creation Error: System.UnauthorizedAccessException: Access to the path '\\KENS-PC\Flight Simulator X\MakeRwys.exe' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.Delete(String path) at g.c(Object A_0, EventArgs A_1)

I've discovered that the culprit is the VAFS5 client on the secondary laptop (connecting via WideFS). I've uploaded a message to the VAFinancials forum to find out if it's a known issue and (perhaps) what can be done to remedy it. Ken

Thank you for the fast replies. Pete, I've needed to perform your suggested action several times to get my updates done. When I've figured out what's going on I'll follow up here. If I can't figure it out I'll just run all my updates from a custom bat file >> guess what the final action will be ~: ) Just joking of course (certainly shouldn't come to that). Best to all, Ken

Several of my utility FSX programs require executing makerwys.exe (in the FSX folder) to update their Nav databases. Before I restart the update process (checking the FSX folder after each program DB update) I thought I'd post this issue to see if anyone else knows more about this issue than I do now. FYI, three of the DB updates (RCV4, FS Flightkeeper, and VAFS5) are being run via WideFS. One DB update (Flight Sim Commander V9) is being run on the primary (FSX) PC. I'm wondering if perhaps the makerwys executable is being moved (vice copied) to another folder (..\windows\Prefetch perhaps) during the update process. Regards, Ken Boardman

Pete and Ian, Thank you again for the IP Address enlightenment. Last time I ran ipconfig I noticed results that included IPv6 followed by hex digits and then scratched my head for a moment. Seems that the FS programs I'm interested in connecting via network mostly still using IPv4. Looks like I'll need to start writing stuff down. I have enough trouble just remembering the decimal addresses LOL!! Best Regards, Ken As a side note, also got Simconnect client connected on the laptop last night >> so now I'm all dressed up with nowhere to go" (need to install some FS programs on laptop ~:)

Thank you for putting that in proper perspective Pete. I was thinking .1 = .10 = .1000000 etc. But now I understand that we are just dealing with whole #s separated by periods ~:) Best regards, Ken

Thank you for pointing me in the right direction Pete. As you can see below, Wide Client is now connecting. I read all the docs that you recommended, then beat up my router (settings) and experimented with varied combinations of Protocol=, ServerIPAdd=, and ServerName= settings in the WideClient.ini file. As you can see, the Protocol and ServerIPAdd settings did the trick, and as unlikely as it may seem, the operation appears to recognize the difference between 192.168.0.1 and 192.168.0.10. Won't connect using 192.168.0.1. Seems very strange to me; but then I'm a bit awkward at this mysterious networking stuff ~:) Now, lets see if some of those FSX utility add-ons will connect from the laptop. I use FS Flightkeeper, ASE, Radar Contact V4 and FS Commander. May also try Servinfo and other VATSIM pograms, although I believe Squawkbox must run on the FSX PC. Please correct me if I'm wrong..... Thanks for all that you do for us. Ken Boardman ********* WideClient Log [version 6.86] Class=FS98MAIN ********* Date (dmy): 30/01/12, Time 18:57:58.127: Client name is WIDEFS1 124 LUA: "C:\WideFS\Initial.LUA": not found 140 Attempting to connect now 140 Trying TCP/IP addr 192.168.0.10, port 8002 ... 140 Connection made okay! 12105 Lost contact with ASE WX requester >>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< My WideClient.ini file contents : ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=195,157,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Protocol=TCP ServerIPAddr=192.168.0.10 ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [sounds] Path=C:\WideFS\Sound\ Device1=Primary Sound Driver Device2=Speakers / Headphones (SigmaTel High Definition Audio CODEC) Device3=HDMI (SigmaTel High Definition Audio CODEC)

Hi Pete, I'm trying to connect a new Win Vista 32 laptop to my Win 7-64 PC with latest (registered) versions of FSUIPC (with integrated WideServer) on the PC; and Wide Client on the laptop. Firewalls are disabled all around and I've tried opening port 8002 via the DLink DLR-825 wireless router's web based interface; however I don't know if I am doing this properly. I have attached a zipfile to this message that includes the latest WideClient logfile, and also a screen capture of my attempt to open port 8002. Any advice will certainly be appreciated. Best regards, Ken Boardman WideFS_1.zip

Hi Pete, Can't seem to raise Marc for an answer. Hoping you can advise me. I just purchased latest version of WideFS and installed the latest FSUIPC version. My FSMeteo Version 7.0 quit downloading (froze during TAF portion of download) after I installed FSUIPC update. Below is copy of my message to Marc: " I just updated to latest payware ver of FSUIPC and purchased Wide FS. Now my FSMeteo Ver 7.0 stopped working properly. When it tries to download the weather, it freezes early in the process > when downloading TAF. Is this a known issue between Ver 7.0 and latest version of FSUIPC? Can you tell me what options I may have to correct this problem >> perhaps revert back to previous FSUIPC version, or update my FSMeteo?" What is best way to correct this problem Pete? Many thanks and best regards, Ken Boardman

Well Pete, I'm excited. I just used FSUIPC to set the "q" key to assign offset 8345 a "1" value as you suggested earlier to disable Gradual Spot View Transition. It works GREAT in the sim. Many thanks, Ken

Thanks Pete, I haven't messed with the buttons, keys, offsets portion of FSUIPC but I'll try to set offset 8345 for a solution. Best regards, Ken

It's saved in the FLT files, and restored when you load a flight. So simply change the option and save the flight. For example [Window.1] ... SpotTransitionType=Fixed SpotFastTransition=True Well, surely a hot key or assignable control would be better? Interestingly the relevant location in FS2004 was discovered recently and mapped in FSUIPC 3.60, so you could actually program it quite easily using the FSUIPC "offset" controls. The offset is 8345 and the byte value to write is 0 for gradual, 1 for transition. You can do it all in the Button and Keys options in FSUIPC. Regards, Pete

Hi Pete, This problem is most likely caused by installation of other 3rd party FS2004 software but I'm trying to troubleshoot to avoid a un/reinstall of the sim (and FSNAV and other goodies). Problem > NAV 1 VOR CDI needle indicates approx 2.5 degrees left when I'm "on course" and the FS GPS path (flight plan generated) and FSNAV match (show me "on course") . Any advice to correct this problem would be greatly appreciated. Do you happen to know what file(s) store the data used to control the CDI needle? Is there one (general) file for all aircraft or does each aircraft have it's own unique NAV 1/VOR/CDI data. Many thanks for of your very fine FS utilities. Best regards, Ken Boardman elsmoko@cox.net