Hello: I'm preparing to set up a home cockpit. What are the basic hardware requirements in setting up client computers? I know I'll need a case, and at least a 1GHZ processor, good video card, and either a hub or cross-over cables, but past that I'm clueless. I've not found any posts on this. Not interested in any particular brands for the hardware at this time, just the basics. Any info past this I would appreciate. Thank you

Generally, the clients are the computers doing all the work. If that is the case then the clients need to be as fast as necessary to perform the tasks they will be asked to accomplish.Servers generally can be slower machines that have software redundancy or an ability to swap in/out hardrives without shutting down the server.If you are intending to LAN the computers, you definitely want a router and not just a hub or crossover cables. If you only have two computers, crossover cables could be used but then you have to manually set IP address. The router provides the necessary IP addresses.I would visit www.schiratti.com/ and look for Wideview information and WideFS information.

Thanks for your reply. I know little or nothing about this networking thing, but my last visit to Shiratti was actually the reason for my post. I actually thought the server would have to be the faster machine. Their new GAIFR panel started me thinking ( always a questionable thing at best). I shall check out their site further. Am planning to perhaps build a modest home sim cockpit. I'd like to experiment using fresnel lenses and multiple monitors. I thought one client operating two monitors, each with the fresnel lens, might work in 2004 with the new features it is supposed to have, therefore my question. I would be thankful for any recommendations on books or websites so this "newbie networker" might learn more. Thanks again

WHAT???????????????????????????"Generally, the clients are the computers doing all the work. If that is the case then the clients need to be as fast as necessary to perform the tasks they will be asked to accomplish."That must be why the 12 servers on the network I work with have 2 to 4 1.2GB PIV Processors and 2GB of RAM each with Win2kAdvSvrSP4 with 2 NAS arrays using RAID 5 carrying 3 bays each with 7 36.4GB HDD and a hot spare on each bay - all hot swappable and the 800 clients are all PIII800MHZ 256MB RAM with Win2kProSP4 on them, because the clients do all the work. What network admin book are you reading?"Servers generally can be slower machines that have software redundancy or an ability to swap in/out hardrives without shutting down the server."See above"If you are intending to LAN the computers, you definitely want a router and not just a hub or crossover cables. If you only have two computers, crossover cables could be used but then you have to manually set IP address. The router provides the necessary IP addresses."WHAT?????A nice fast switch would be much better and routers have nothing at all to do with providing IP addresses any more than my uncle Fred does. You figure out your own IP address scheme and then configure the network parts to use the scheme you have set up. A router divides network segments. What is there to segment in a home cockpit? You gonna have more than 100 connections per segment?I would imagine in building a home cockpit one very, very fast PC with a lot of RAM and a large number of usb ports would be all that is necessary, but since I am not into that, I do not know precisely. I do, however know just a little about networking and that is not what is necessary here.I looked at the site Schiratti site and they are using FS98 with PII computers. USB wasn't even available back in those days. Good grief!!! Get some real help - go to the AVSIM: The Home Cockpit Support Forum and ask around there. I am sure they can make it a lot easier than trying to network your whole neighborhood. Also, take a look at www.flightdecksolutions.com and http://www.goflightinc.com/ and http://www.flypfc.com/.Clients more powerful than the server,,,,PLEASE!!!!

You seem to infinitely more knowledgeable about LANs than me, so I cede to you to provide better information.However, I object the manner in which you present your case!

Hello: As six days had passed, I had assumed that this was either such a newbie question that it was not worth a response, or that I should have posted it elsewhere. I certainly do not wish to start any thread which balloons into anything other than a pleasant exchange of ideas. My sincere thanks to wsieffert for responding to my post, and trying to help. My thanks also go to tgabriel for his expert help, albeit in a somewhat controversial tone re wsieffert's response to my original question. I shall take what I have learned here and go forward, hopefully posting some shots in home cockpit builders forum. Thank you both again.

First of all, I was expressing my utter astonsihment about the information in the response to your inquiry. I regret that you perceived my response in a negative light. I am certainly NOT a networking expert, but I do know when I see obvious, glaring inaccuracies that can come to much more harm than good. If your feelings or wsieffert's were hurt, that is unfortunate but when I see recommendations that are downright wrong, I get a little out of sorts.As I stated in my response, the group that deals with simulated cockpits might be a better place to get help in configuring one. Also, as I stated, there are several Internet sites that provide a wealth of information to enable you to do this kind of thing and I provided links to them. Something else I did not state is that Google searches on home cockpit sources of info might reveal a gold mine of "real" experts. :D :D :D

Here is another link that might be very useful. I have scanned over the site, but, since my interests are not here in depth, I have not read it all. It might help you, however: http://www.mikesflightdeck.com/