camaflight

No, I can't see the three mode states as Joy#xx button #8xx, xx and xx". And Pete, please, I allways try for myself, I'm sitting here (alone :o ) and try for myself over and over again, then I saw this post and by jumping into it I hoped I could gather some more info. And thanks, so I did. I will look into the Lua plug-in and Paul's way as the mode states are not visible. I'll never looked into this Lua thing and I don't really know it's capacity, but I will look..and learn... Regards, Carl

Hello Pete, does that mean it should be possible to make the mode selector visible in FSUIPC 3.998q's Buttons & Switches assignments tab? Or maybe I misunderstand what this is..... Regards, Carl

Paul, thanks again. I'll make a forum search although I think I've seen that post allready. I'm afraid that was FSX - FSUIPCX related. I do a search though. I will also take the time to study your solution - sooner or later I have to take the step towards your level ;) Regards, Carl

Hi Paul, thank you so much for responding to my question here. Realizing that I will need some time getting the grasp of your coding I don't want to postpone thanking you until I'll be that far. There are obviously some differences between FSX with FSUIPC 4.xxx and FS9 with FSUIPC 3.xxx. As an example I can't see the mode selector visible in FSUIPC's Buttons & Switches assignments tab from the latest version of FSUIPC. However, as mentioned I will need some time understanding your way of doing it. As you know; the Saitek yoke has a button-wheel allowing you to switch between 3 available modes which again makes it possible to asssign every other buttons for three different purposes depending on the mode in use. This is possible when using the Saitek assignment programming tool. However, I would much more take the FSUIPC fully in use leaving both the Saitek and the FS way "in rest". I'm not quite sure if my additional information here makes any difference regarding your answer. If so I would very much appreciate you giving a signal about that as I'm pretty much a novice when it comes to handle such problems as you are capable of. Best regards, Carl

Hello and Happy New Year, I'm running FS 2004 and wonder if it's possible making different assignments for the same button by changing mode. I also have the Saitek Yoke and throttle quadrants. Regards, Carl

Yes, absolutly all your suggestions have been tried out. Sorry I haven't been quite clear about that I have carried out tests in between. :wink: I will follow your newest suggestions as well. Before that it would be really interesting to know if there actually is some unsolved or perhaps poorly developed network linkage between Vista Home Premium and XP Pro. Another option for me is to upgrade to Windows 7 as I receive my W7 shortly. Then I could consider upgrading my old computer with W7 as well (just have to run a feasible test first). Regards, Carl

No. Ok I looked it up; it was "ProtocolPreferred=" not "PreferredProtocol=". It didn't help I'm afraid. Everything you have suggested I have tried. Unfortunately I have so far no success with my network setup in order to take use of WideFS. Regards, Carl

But, I have done so ! - at both ends - as regards speed/duplex settings; set to 100 Mbps full duplex instead. Please confer: No, of course I haven't been messing with it. The reason I didask was that you told me to try changing the "PreferredProtocol=" from TCP to UDP and I didn,t find that line PreferredProtocol=" in the server ini. So I just wanted check if there was anything wrong with the server ini I have. That's all. Regards, Carl

I'm not finnished with the UDP test yet. So many new variables pop up so I have to slow down a little and take fewer things at a time: Not really, the Wide Client log told 357 sec. I never looked at the log regarding this before, just clocked it myself figuring out it was something between 31/2 to 5 minutes. I think we should consider that as the same. Yes it was ! ---------------------------------------------- Furthermore - from the server log this was the result: Throughput maximum achieved: 2 frames/sec, 172 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 7 bytes/sec Average receive rate from "KONTORET": 0 frames/sec, 8 bytes/sec Last time I had 34 frames Max (FS limited to 31), 7 frames min, 11 frames average. I discovered a new thing: WideClient isn't totally frozen after all. It will be impossible to shut down and it will be impossible to move the WideClient window around at the desktop or restore it when minimized. I discovered this by turning FS off, and then looking at the logs showed that this was registrated as much as it was registrated when I started FS again and once more shut it down. What was impossible though was starting an application - it stated "not connected to FS". The only way to get an application connected for a few minutes again is to reboot the client machine. So, some questions if I may; For the network adapter there is an option to set the Speed & Duplex to even 1.000mbps full duplex on both ends. Would that make any difference you think? When looking in the WideFS technical manual there is a section where some users have made adjustments to exactly the advanced network adapter settings. As I have dual network adapters build into the motherboard this section could absolutly be relevant to me. However, as stated before; this is stuff I don't understand too much from. The properties as regards the advanced settings for the one adapter I have in use are with options respectivly as follows: (present settings in bold) Energy Star -------------------------- Disabled / Enabled Flow Control--------------------------Tx & Rx Enabled / Disabled Interrupt Moderation--------------Disabled / Enabled IPv4 Checksum Offload----------- Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Jumbo Packet-------------------------1514 Bytes / 4088 Bytes / 9014 Bytes Large Send Offload (IPv4)---------Disabled / Enabled Log Status Maessages--------------All Maessages / Errors / None / Status Messages / Warnings Max IRQ per sec----------------------1000......5000........30000 Network Address--------------------Value / Not Present Priority & VLAN----------------------Priority & VLAN Disabled / Priority & VLAN Enabled / Priority Enabled / VLAN Enabled Receive Buffers----------------------256........512 Speed & Duplex----------------------10 Mbps Full Duplex / 10 Mbps Half Duplex / 100 Mbps Full Duplex / 100 Mbps Half Duplex / 1000 Mbps Full Duplex / Auto-Negotiation TCP Checksum Offload (IPv4)---Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Transmit Buffers--------------------256........512 UDP Checksum Offload (IPv4)---Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Wake From Shutdown--------------Off / On Wake-Up Capabilities--------------Link Change / Magic packet / Magic Packet & Pattern Match / None / Pattern Match Do you have any idea what should be done here if anything ? Regards, Carl Oh, I forgot something; Here is a copy of the server ini: [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [ClientNames] 1=xxxxxx Is this basically OK. I will test the UDP the next thing. Carl

Hi Pete, seems an effect of putting my question in a new topic bridged the original topic about this issue over here. To add some new info here. I just started WideClient without any client applications - just WideClient connected to FS. After 31/2 to 5 minutes WideClient got frozen. This doesen't indicate anything wrong with what you tell; it just tells that there is no que created because of any client application alone. I try to be a little restrictive with bringing into the discussion things I pick up on the net. Being no capasity on computers I may mix in stuff that's completely way off. Nevertheless, reading through the server log from the the last try running only WideClient I found this: " 2046327 Error 10054: client socket disconnected at Client: removing (skt=10228) TCP" Then searching for error 10054 I found inter alia these links: - http://go.microsoft.com/fwlink?ProdN...4&LinkId=20476 - http://support.microsoft.com/?kbid=919710 - http://support.microsoft.com/?kbid=942861 I have done that and no memory leak is indicated. In fact memory usage is quite low. Okidoki, checking now. Haven't tried that. I'm not experienced with this but I will read, learn and do now. Wow, that gave me an instant feeling of proudness being at the same level as you. Very short moment I'm afraid.......... Regards, Carl

Hi Dave, thanks for responding. I'm not sure were to find the WideFS related info on that site though. Another thing, that I'm frankly not quite sure about, is that Vista Ultimate is probably a total different OS than Vista Home Premium when it comes to networking against a XP machine. But I'm emphasising that this is only an impression I got reading through a huge number of related ( and quasi related) topics on the net. Hope you can give me a lead where to search on the given link. Kind regards, Carl

Hi all, I'm still having problems running applications on the WdeClient macine (the applications loose contact with FS after 31/2 to 5 minutes). I have also great difficulties in finding out if my two OS's really are capabel of running with the WideFS. Hence I wonder: Could those of you who reads this topic please tell if you have managed or not to run WideFS with the same configuration as I do: WideFS-server machine: Vista Home premium 64 Bit WideClient machine: XP Pro 32 Bit I just need to know if you succeeded or not, but of course if you have the time then just briefly tell what you did to achieve this and/or if there were any particular problems that occured during the set up process. Thanks in advance Kind regards, Carl

Ok, I will work on this. I think I also will try my old router as a second router to use between the two machines "only". I had already set upper limit for FPS i FS to 31. You're really a stayer Pete still keeping up with my issue, you know I'm grateful ! Regards, Carl

Hello again, well now things begin to happen. I have reset the network settings back to square one and started all over again and done so several times without any success. Then as repeating the normal settings for share permissions to aapropriate folders, one at a time, Vista suddenly started processing share permissions to all files within respective folders. Until now that hadn't happened ! I have done absolutely nothing else than starting all over again several times doing excact the same settings time after time. After this ASv6.5 started and loaded weather. RC started and worked from my clien computer with sound and everything - until ASV6.5 broke down with a frozen WideClient after a couple of minutes. I then looked at the server ini and everything seemed to work very nice in the beginning, giving 34 frames at maximum, but of course 0 at the end. However, I noticed one more thing in the ini as follows: ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 03/11/09, Time 10:18:40.300: Server name is xxxxxx 95628 Initialising TCP/IP server 95628 Initialising IPX/SPX server 95628 IPX/SPX socket() failed [Error=10044] Socket type not supported 95628 Failed to start IPX/SPX Server 95628 Initialising UDP/IP server 96595 Broadcasting service every 1000 mSecs 98124 Incoming connection Accepted ok (skt=10208) TCP 98358 Connected to computer "KONTORET" running WideClient version 6.787 (skt=10208) TCP 717433 Error 10053: client socket disconnected at Client: removing (skt=10208) TCP What does the error messages in bold, cursive letters mean ? Is this normal messages or does they tell something is wrong with the connection ? Regards, Carl EDIT: I have now run FS Smooth and AI Separation on the WideClient. This worked fine 4-5 minutes and then FS got disconnected and WideFS was frozen. As with the AS and RC WideFS says it's connected, however it's also frozen at the same time FS gets disconnected.

Ok thanks Pete, the more I read about this the more I suspect that I have bought the wrong version of Vista. I asked spesifically about networking capabilities between XP and Vista with the retailer, but obviously not specific enough. If I should manage to set up a acceptable network and permissions for my client applications then I will come back and tell how I did it. There may be some others experience the same problem as I do. Regards, Carl

A good idea. The case is, however, that I deleted all shares and settings for my network to build it up from scratch again following Microsoft and other links about how to do this. I have the Vista Home Premium and it seems that all none-business Vista versions have a serious lack of possibilities to setting up permissions between two or more networked computers. It's unbeleivable how bad quality Microsoft has put into their help desk system. And it's discouraging to read Microsofts statements " No way to do or access this or that in Vista starter, Home Edition or Home Premium...." Networking is obviously a part of Vista Home range that doesn't seem to work easily or perhaps don't work at all. On top of this it's of course an additional problem that I'm a novise as regards network setup. Well enough of whining, that won't help in any case. One question about WideFS, does the WideServer also need to be the server machine in the Windows network ? I must say this is also a thing that confuses me, because one place Microsoft calls the main computer (for me I want that to be my new Vista computer which also is the FS machine) the server computer, another place they call the main computer the client. They also do mix this with what WideFS calls the client (WideClient machine) calling that the Remote Desktop and sometimes the client...... Well, I have chosen for my FS-machine the IP 192.168.1.2 and the WideClient machine IP 192.168.1.3. The reason is that my router has hardcoded (I believe) the IP to be 192.168.1.1 and without having the two other IP adresses as mentioned above Windows won't let me have acess to internet from neither of my computers. When letting Windows choose IP adresses automatically the adresses will be as described anyway. I hope this will be OK with WideFS ? Without having tested what you asked for in your last reply (as quoted) I think maybe that the reason why I can't get ASv6.5 to work properly and RCv4.3 to work at all is one and alone that I do not get access to "C:\Users\MyUserName\Documents\Flight Simulator Files\". Does anyone know how it is possible to get read/write permission to this folder from the WideClient machine when that machine is a XP Professional ? As you see I'm not giving up on this matter. It helps a lot though to get some help and attention so I'm very grateful for that. Regards, Carl

I haven't done anything with the active radar- not installed it. Perhaps AS is searching for something connected to the active radar and I have misunderstood that active radar is mandatory to install. I will investigate this the first thing, also if some old elements from any prior versions of AS still are present; any files or strings in the registry. Regards, Carl I have done as I described above except installing active radar. On fresh booted machines AS gets connected with FS and works seemigly fine until reading so called station data ( I assume you recall this from your own AS). AS then freezes sometime during this read process and WideClient also freezes. When ending all; AS, WideClient and FS then restarting WideClient then WideClient seems to be OK until FS is started and WideClient gets connected. Thereafter WideClient gets prompt frozen. When rebooting evrything is back to as descrbed. However, I now skipped the AS and tried running RC4.3 (Radar Contact) from fresh booted machines the in the same order as before, only RC instead of AS. One of the nice things with RC is that when something goes wrong you will get an error window popping up telling you what kind of runtime error you have got. I got the runtime error 75: Path/File access error Program does not have rights or access to a file. Often this is caused when a program is trying to access a network file it doesn't have proper access to either because of network privileges or something is blocking the program. This issue can also be caused when the file is being used by another program or is read-only. No doubt now I guess, what I struggle with is a bad network setup. I just can't see what I have been missing. Maybe I should clean up all workgroups and network settings and start all over again. Regards, Carl

Hello Pete, I haven't done anything with the active radar- not installed it. Perhaps AS is searching for something connected to the active radar and I have misunderstood that active radar is mandatory to install. I will investigate this the first thing, also if some old elements from any prior versions of AS still are present; any files or strings in the registry. Regards, Carl

Hi Pete, it certainly is good to here I'm not alone with this trouble. I won't give up, I seldom do - I'm afraid - but I surely still hope Windows7 can loose up these things at least a little bit if I haven't managed to crack the nut before it is installed. Ok now, here's what AS wants access to: Installing ASv6.5 on a networked computer over WideFS 1. On the separate non-FS computer, unpack the installation .zip file to a temporary location, such as C:\ASTEMP (Do not install ASv6.5 on the FS computer). 2. Run the Setup.exe program to launch the installation process. 3. Follow the on-screen prompts. 4. Setup networking and sharing so both computers have full access to each other, especially in all FS and ASv6 related paths. You will need to share the ASv6 Folder (on the ASv6.5/WideFS computer) and the FS Folder (on the FS computer) as well as the Application Data Folder (in the FS computer’s Documents & Settings\User Name Location), or share the root drives (i.e. C:\) directly. For more help with networking WideFS, please see the WideFS documentation. 5. On the FS computer, browse to the networked ASv6 install folder and run the ActiveRadarConnector.exe program. 6. Follow the on-screen prompts to locate the appropriate paths/files, copy required data, and test the installation. 7. If the installation fails for any reason, see the ActiveRadarConnector.txt file for additional information and alternative installation methods. 8. Proceed with Configuring FSUIPC and FS. Yes it surely looks like. I will update this thread as soon as I get a brakethrough or have some intermediate interesting adequate issues that hopefully would give a clue on what's going on. Kindly regards, Carl

Yes, I think now that this is a pure network problem where at least WideFS is an innocent part. Meanwhile I have tryed checking that I have both read/write permissions from the client machine to the server machine. I have set the client machine to be co-owner for the folders requiered to use by AS. After doing so AS got further than ever before. AS got connected to FS at once and started loading weather data concerning the airport in use. It downloaded all 400K or so. Then when finishing the process with the "nearby" airports it suddenly got disconnected from FS. I read throgh the server ini file afterwards and it showed that frames ended with 0, but maximum was 31 which is exactely the FPS limit I presently have. I never had that high frames in the server ini. I assume you have noticed that I am a novice with computers or to justify my own skills a little - a novice on computer network. I wonder if I should wait for the Windows 7 to arrive in my briefcase. My computer is complete new and Vista Home Premium was installed just few days prior to my diving into this issue. Based on this I have doubts about that this can be a driver problem. I have two network addapters on my new server machine, one with IPv4 and one with IPv6. The latter is listed as limited and the IPv4 is listed as local. I don't know what this means, but I have switch between the ports to check if the situation differs with use of the other network connection. What happens is that when testing WideFS, FS and AS, then AS get connected with FS again but disconnects shortly after with a frozen WideFS as result. After such an event AS will not connect to FS again when re-testing. To achieve any FS connection for AS again I will have to reboot both machines. It still may be something missing in my network setup regarding read/write permissions. I find it very complex and complicated to follow guidelines in Vista. These guidelines are also hard to find sometimes and they mix expressions for one and the same thing sometimes. This gives me a hard time. Well that's it I'm afraid, but I really appreciate that you have given so much time on this issue Pete. Thanks alot. Kind regards, Carl

Hi, sorry, I used the search function searching for terminate....... - it was a wrong expression of me using looking through. I shut down the WidefsClient by using task manager - end task or end process. Regards, Carl

Hello, I have now done following: - Set log=debugall in ini-file - started WideClient - started FS on server - started AS on client - shut down AS on client - shut down WideClient (- shut down FS on server) Result: + Wideclient started normal + WideClient got connected + AS started normal and showed connection to FS - AS disconnected for some reason and never read the weather data for running airport on FS - WideClient window was frozen again (occupied with something) and I had to end it with task manager. I did not find out how to do this although I looked throgh both the user guide and the technical manual. I have attached the log file both for client and server. I'm afraid I didn't think about changing the server ini with "debugall" - it only ran with default "Errors+" Regards, Carl INI FILES 28.10.09-1.zip

Hi Pete, :shock: I look at the watch. My wife told me before she went to bed hours ago that maybe I should look for bad connections in my head instead in the computer. She was sure at least the computer wanted badly to go to sleep.......... Women, they have no understanding for what's really important in life :roll: Well, I'm trying to run ASv6.5. I used to have FS on the client machine, so I uninstalled the ASv6.5 and made a new fresh install with a setup I got few days ago from HiFi. I have followed the advice in Wide FS manual and installed the client and ASv6.5 in the same folder. Attached you will find the log. I firstly adjuseted the cfg-setting to log=debug. One time the WideClient was OK before I ran the application, the other tests it happend before. Hence, there really is some faulty network connection. Computer names and the common workgroup name :lol: are all OK. Tomorrow in broad daylight I will specify the ServerName and Protocol in the client's INI file and see what happens. Thanks, you help keeping my spirit up, Carl WideClient.zip

Hi, I am pretty sure then that this has something to do with the network I have tried to set up. I think I have really messed things up here now as it seems getting worse and worse. The log file got very large in some few minutes. However, I think I will only waste your time looking into this anymore until I have made the network setup with some experienced on site help. The WideClient (and window) was OK half a minute or so after connecting, but then was totally frozen again. I come back again if there still are issues after the network has been successfully set up. It was this problem getting Vista to recognize and implement the client computer on the network map. I installed now the hotfix from following link; http://support.microsoft.com/kb/922120/en-us and when checking the network map afterwords the client was there. Unfortunately I have one or two more miles to go before I can let my frustration out in making a very hard landing some place. Regards, Carl

Hello, I have searched the forum and couldn't find anything that was adequate to my isseue here. After starting WideClient but before it gets connected it is possible to minimize or drag the WideClient window around the screen. However, after it get connected the window is frozen - not possible to drag around, it is impossible to minimize it and at the end complete impossible to shut down without using Windows task manager. Any idea whats wrong ? In case this is a network problem this may then be due to the fact that I have still a connecting problem between client and server. I don't get appropriate permissions from client to server. There is a known problem here because of XP (client) and server (Vista) for which Microsoft has a solution they do not reccommend if the problem isn't exactely as they have described - and I'm uncertain if it really is. They then reccommend waiting for an official update, which I reccon will be my upgrade to Windows 7 in a few weeks when cd is received. Carl