Hello, After my recent computer upgrade, I have enough components to build a second rig. I'm considering networking this second computer to run my other addons such as ASA, Radar Contact and maybe use it to display navigational charts. I'd appreciate any input from those of you who are using it. Does it improve FSX performance by moving your addon programs to another computer? Thanks

Hi Mike,I just bought a new PC too and bought WideFS last Tuesday, still trying to figure how to make it work, the manual explain WHY it does it's job but not really how, like click there, modify properties of this file, etc. Both PC are in a network and i can transfer files just fine but WideFS is a mystery or i am just too dumb :( If someone would be kind enough to write a short tutorial, it would be much appreciate, i miss Radar Contact :( Alain from Montreal

Can't help with RC. ASA uses Simconnect, so there's no requirement for WideFS. I use it for FS Commander Flight Planner [and moving map] and as a dedicated Moving Map application for use on my 1:500000 UK VFR Charts, which a major retailer here in UK says "can't be done" :( or Fugawi maps for general land based "stuff". I send the GPS data from FSUIPC over widefs, but you require a virtual serial port [or I do as the 2nd machine is a laptop] and I don't have "real" serial ports at either end. I use the MixW driver, "invented" primarily for Radio Amateurs. This only works with 32 bit clients. I have yet to find a freeware virtual serial port for 64 bit. I have Vista 64 as the FSX OS and Vista 32 on the laptop, works a treat. HTH.Maurice.

...bought WideFS last Tuesday, still trying to figure how to make it work, the manual explain WHY it does it's job but not really how, like click there, modify properties of this file, etc.

Normally, 99% of the time, you need do no clicking, modifying, nothing. Once you enable WideServer (in FSUIPC's options), that should be it. It is all designed to be invisible, behind the scenes, automatic.If there is any reason why the Client PC can't find the Server PC (and it will tell you if it can't, in its Log file -- all my programs produce Log files to tell you exactly what is going on!), then you might be more successful telling WideClient exactly where the Server is and what Protocol to use. That is clearly described in the User Guide -- just a matter of entering two lines (ServerName=... and Protocol= ...) into the WideClient.INI file.The usual reason, these days, for any difficulty, is that Microsoft, in their infinite wisdom, decided that the default WorkGroup name for Vista and Win7 be different from that used in XP for so long. Many folks never bother to change their WorkGroup names, and if they don't match the Broadcasting from the Server doesn't work, so the Client never sees it identifying itself. You can make the WorkGroup names match -- change it in My Computer properties in the same place that you give your Computer name. That might be better in the long term.Incidentally, the Support I offer is second to none, but it is really over in the advertised and linked Support Forum. Unless I am on holiday or sleeping at the time you will always get an answer within hours, if not minutes.

Both PC are in a network and i can transfer files just fine but WideFS is a mystery or i am just too dumb :(

Maybe a little dumb not asking the question, and not in the right place, instead of being mystified?

If someone would be kind enough to write a short tutorial, it would be much appreciate

Shouldn't be needed. But now you are an expert on getting Windows Explorer to easily see and transfer files from other PCs, can you tell me how? I have a nice new Win7 PC, working fine, no firewall, no UAC. Explorer sees itself and another Win7 PC, but doesn't see any of my XP PCs -- unless i explicitly open them via \\name. Then everything opens up.On my two other Win7 PCs, all the other PCs on the Network are always seen, no problem. It's just this one. What makes the difference? I can't find one. Can you advise?RegardsPete

I use the MixW driver, "invented" primarily for Radio Amateurs. This only works with 32 bit clients. I have yet to find a freeware virtual serial port for 64 bit. I have Vista 64 as the FSX OS and Vista 32 on the laptop, works a treat.

You got MixW working on Vista32? I couldn't!For 64-bit the only one I found at a reasonable price, not free, was the Eterlogic one at $25. I mention this one on my Support Forum, with a link.RegardsPete

You got MixW working on Vista32? I couldn't!For 64-bit the only one I found at a reasonable price, not free, was the Eterlogic one at $25. I mention this one on my Support Forum, with a link.RegardsPete

Good evening Pete,Do you know, I don't think I have ever *posted* over on your forum - at least, I cannot remember so doing and I have been an FSUIPC user for rather a long time now. I do try to RTFM before I shout, so it can't be that difficult, can it? The only issue I have had was when some version or another completely changed the look of the FSUIPC config file and my diabolical short term memory. I will "dig out" my config files for both bits of software that give me the "can see/talk" with MixW and mail them to you. They are about as minimalistic as you can get - I haven't used the "advanced" features of FSUIPC, I can't even remember why I purchased it. I'll lay a fiver that there's nothing in there you haven't tried, but it won't take long to find/zip/send and when you read them, you can bin them. They certainly work for me.Thanks for the link to the 64 bit port software, I shall bumble along over there for a look-see. I'm not doing much in FS recently, but with the darker evenings etc, this is surely about to change.Maurice.

Normally, 99% of the time, you need do no clicking, modifying, nothing. Once you enable WideServer (in FSUIPC's options), that should be it. It is all designed to be invisible, behind the scenes, automatic.

Thanks for responding Peter !By enable WideServer in FSUIPC you do not mean registering it right ? both are by the way.

If there is any reason why the Client PC can't find the Server PC (and it will tell you if it can't, in its Log file -- all my programs produce Log files to tell you exactly what is going on!), then you might be more successful telling WideClient exactly where the Server is and what Protocol to use. That is clearly described in the User Guide -- just a matter of entering two lines (ServerName=... and Protocol= ...) into the WideClient.INI file.

I did enter those two lines in the INI file...

The usual reason, these days, for any difficulty, is that Microsoft, in their infinite wisdom, decided that the default WorkGroup name for Vista and Win7 be different from that used in XP for so long. Many folks never bother to change their WorkGroup names, and if they don't match the Broadcasting from the Server doesn't work, so the Client never sees it identifying itself. You can make the WorkGroup names match -- change it in My Computer properties in the same place that you give your Computer name. That might be better in the long term.Incidentally, the Support I offer is second to none, but it is really over in the advertised and linked Support Forum. Unless I am on holiday or sleeping at the time you will always get an answer within hours, if not minutes.Maybe a little dumb not asking the question, and not in the right place, instead of being mystified?

Having bought both products thru Simmarket, i didn't know you had a forum :(

Shouldn't be needed. But now you are an expert on getting Windows Explorer to easily see and transfer files from other PCs, can you tell me how? I have a nice new Win7 PC, working fine, no firewall, no UAC. Explorer sees itself and another Win7 PC, but doesn't see any of my XP PCs -- unless i explicitly open them via \\name. Then everything opens up.On my two other Win7 PCs, all the other PCs on the Network are always seen, no problem. It's just this one. What makes the difference? I can't find one. Can you advise?RegardsPete

All my 3 PC ( old an new plus my wife's) are on Vista on the same network, my son's is on XP, let me try to check it out this week end and get back to you. I bought both products tuesday morning before going to work and spend maybe an hour at night reading the manual and experiment, i must be very close, just one more question and i will register tou your forum for the others: Wide client needs to be on the second PC right? thanksAlain from Montreal

Do you know, I don't think I have ever *posted* over on your forum - at least, I cannot remember so doing and I have been an FSUIPC user for rather a long time now.

Great, so never any questions or problems. That's fine by me! ;-)

The only issue I have had was when some version or another completely changed the look of the FSUIPC config file

That's actually never ever happened. It's been onward compatibile, incremental changes, since version 1.00 in 1999.

I will "dig out" my config files for both bits of software that give me the "can see/talk" with MixW and mail them to you.

I think you misunderstood me. I thought it was MixW which simply would not create any virtual ports when installed in Vista. I've no problems with the freeware Eterlogic one in any Windows version. This is why I advise Vista users to go for Eterlogic.RegardsPete

By enable WideServer in FSUIPC you do not mean registering it right ? both are by the way.

WideServer for FSX is built into FSUIPC4. After registering it may or may not be enabled. There's a button on the first tab (About) in FSUIPC options. If it says something like "Enable WideFS" then click it to enable WideFS.

Having bought both products thru Simmarket, i didn't know you had a forum :(

Oh dear. The documentation tells you (right at the beginning), the main "About" tab in FSUIPC options tells you (just below the version number and date), the download site at Schiratti tells you, and has a button to get there, and, perhaps astonishingly, the pages where you actually bought them, in SimMarket, has this line reasonably prominently displayed:SUPPORT http://forums.simflight.com/viewforum.php?f=54

All my 3 PC ( old an new plus my wife's) are on Vista on the same network

It isn't the "same network" that matters, it is the WorkGroup name which is relevant, as I said.

Wide client needs to be on the second PC right?

WideClient is run on any client PC, not running FS, on which you want to run things connecting to FS on the Server PC, the one running FS and therefore FSUIPC and WideServer. If you've not run WideClient on a connected PC, then it isn't surprising it cannot connect! ;-)RegardsPete

Just did the same thing.Not much to it.Installed WideFS6 on both computers for FS9.Installed WideFS7 on both computers for FSX.Start FS?On your secondary computer double click on WideFS6 OR WideFS7 depending upon which FS you selected and wait for it to connect.Start the relative program or programs.Have a ball flying.I have FDC, FSC, and PF3000/PFE operating on my secondary computer. I was debating Active Sky (for the secondary computer), but if I understand correctly none of this is required for it anyway.Any other suggestions for FS Addons on the secondary?Good luck:RTHAdded note: If you decide to go the two computer route, I highly recommend the freeware program, "Synergy" which will allow you to use a single keyboard and mouse for both computers. The only glitch to this, is that with some the computer will not start up without having a keyboard connected and the union does not complete until both are up and running. I started out with an old AMD 1.2 unit and it required the keyboard to boot up. I replaced it with a P5N-SLI unit. Upon bootup it will say that there is no keyboard present during the bootup, but will go ahead and start up. As soon as it is booted up, SYNERGY connects the primary keyboard and mouse to the secondary computer. The only other item is that with NOD32, the firewall will prevent the connection. Solution:1. Start up the primary computer.2. Disable the NOD32 firewall (Right click the icon in the tray)3. Start up the secondary computer. and wait a split second for the connection.4. Enable the NOD32 Firewall. The keyboard and mouse connection will be retained.Good luck:RTH

Mr Dowson;There is no need to be condescending; like i said, i downloaded the products, i already know how FSUIPC works as i have bought it for FS9 a couple of years ago, but not WideFS. i read the manual quickly and got some of it but not all i guess..You know what ? I was not expecting you to answer here, i respectfully tried to get some answers (on the wrong forum according to you...) and i feel like being treated like a child from you ! so i do not think i will register to your forum and get the same attitude.the products are good no doubt but i still wish i could get a refund from simmarket....if you wish to further comment on this post, please send me a private message.I will try to sort it out on my own, unless somebody else will be kind enough to help here at Avsim.Regards Alain from MontrealEDIT : Thank you very much Mr. Hodges! that should do it !Clear and concise... :( Mwilk, sorry for all this....Alain from Montreal

and i feel like being treated like a child from you ! so i do not think i will register to your forum and get the same attitude.the products are good no doubt but i still wish i could get a refund from simmarket....

Well, isn't that just a bit childish? :(

n4gix, as a paying customer, i think that i am entitled to have: 1) a working product as advertised (which in this case i have no doubt it works)2) courteous customer service in case there is a problemWhen one or both of these conditions are not present, why is it childish to wish being able to get a refund ?If i would have witness similar behaviour from this developper BEFORE making the purchase, i would certainly hesitate encouraging that entreprise..Respectfully,Alain from MontrealPS i think i realise what might have cause this, maybe Mr Dowson felt that if i did not register to his forum was because my software was not genuine ? if that is the case, i would gladly supply the order # from Simmarket, at is conveniance.

Just did the same thing.Not much to it.Installed WideFS6 on both computers for FS9.Installed WideFS7 on both computers for FSX.

Actually, just to simplify this, if you mean WideClient, then this, the client program for all versions of FS, is the same program. The only difference between WideFS6 and WideFS7 is in the Server, the part which sits in FS. All of your client computers can connect to any of FS98, CFS1, FS2000, CFS2, FS2002, FS2004, FSX or ESP, without any change in the client software.RegardsPete

Thanks for the clarification Pete.Regarding what I interpret to be a flame:I have asked a pretty dumb question or two to Pete, and he has been patient and kind in his response leading me to the proper place in the FS hanger. Not only childish, but I highly suspect a bit of provocation has been communicated if a response was anything but courteous and informative. In my book, he is one of the icons of what should be in FS.As always Pete, thank you for your great contribution to FS and your help when I have needed it.Respectfully:RTH

Actually, just to simplify this, if you mean WideClient, then this, the client program for all versions of FS, is the same program. The only difference between WideFS6 and WideFS7 is in the Server, the part which sits in FS. All of your client computers can connect to any of FS98, CFS1, FS2000, CFS2, FS2002, FS2004, FSX or ESP, without any change in the client software.RegardsPete

There is absolutely no "flame " in what i wrote, i did not diminished neither the product or it's developper?! Since it seems that i was not understood Let me try to explain the situation the way is saw it:I purchased FSUIPC and WideFS for FSX tuesday morning, right before going to work; back at home at night i installed the program in FSX module folder and tried to connect with my second PC wich i also installed the Wideclient as required. i briefly read the Widefs manual and tried to config server and client, wich i failed....Found this post today and replied, then Mr Dowson replied, stating and i quote "Maybe a little dumb not asking the question, and not in the right place, instead of being mystified?" Okay, maybe i asked for it myself by saying i was dumb not understanding the manual....so i tried in a respectfull manner to get more infos from Mr. Dawson only to be shown that i am even more dumb not to have noticed the support links to his forums ?! That is why i am dissapointed; in my book, if a customer ask a question, does not matter if it was covered elsewhere ad-nauseam, a developper should show patience and understanding, not all of us are able to program but, being a mechanic by trade, how many of you know how to reassemble a car engine from scratch and make it run properly ? i can but for me, a PC is a little more challenging... i just replace the motherboard from my new HP (there is a known defect in the new e9180f from HP but that is another story..) with an Asus Rampage and i was scare as Heck that it would not work !!!I understand and fully agree that Mr Dowson work is very good, using FSUIPC since 2005 with FS9, it is only sad we were not able to understand each other.All i was asking was a simple answer, like Mr Hodges did, to show me what was missing. Now back to try making it work...Alain from Montreal