Joined: Nov 30, 2006 Posts: 129 Location: UNITED KINGDOM , HERTFORDSHIRE
Posted: Sun May 18, 2008 12:37 am Post subject: Vatsim Downloads
Hi All
Vatsim Downloads i know you need to download and installing two programs. FSCopilot and FSInn.
But i see that :- Minimum Requirements:
Windows 98SE, Windows ME, Windows 2000, NT or XP
Microsoft Flight Simulator 2002 or 2004 or FSX
Which i have Microsoft Flight Simulator 2004 and FSX, on Windows XP which i know if i download FSCopilot and FSInn. would work with XP.
But i use Microsoft Flight Simulator FSX, on Windows Vista more than i do on the XP.
Would FSCopilot and FSInn work with Windows Vista ?. _________________ viper1 " Martin Alan Dilley"
Joined: Feb 25, 2006 Posts: 321 Location: Perth, Western Australia
Posted: Sun May 18, 2008 3:03 pm Post subject:
Hi Marty
My PC details can be found here to use as a refrence http://www.ausflightsim.net/ftopict-2375.html Please note that I have upgraded to 4GB's of Corsair 1333 RAM and the OS is now 64Bit Vista Ultimate since this post was made.
Pros & Cons
In short, performance is the main reason behind my choice of using a 64bit OS. The downside is compatability with common products and devices. e.g. Most Ethernet ADSL modems wont work under a 64bit OS.
For a more detailed responce read on.
A common misconception is that 64-bit architectures are no better than 32-bit architectures unless the computer has more than 4 GB of memory. This is not entirely true:
Some operating systems reserve portions of process address space for OS use, effectively reducing the total address space available for mapping memory for user programs. For instance, Windows XP DLLs and userland OS components are mapped into each process's address space, leaving only 2 to 3.8 GB (depending on the settings) address space available, even if the computer has 4 GB of RAM. This restriction is not present in 64-bit Windows.
Memory-mapped files are becoming less useful with 32-bit architectures, especially with the introduction of relatively cheap recordable DVD technology. A 4 GB file is no longer uncommon, and such large files cannot be memory mapped easily to 32-bit architectures; only a region of the file can be mapped into the address space, and to access such a file by memory mapping, those regions will have to be mapped into and out of the address space as needed. This is a problem, as memory mapping remains one of the most efficient disk-to-memory methods, when properly implemented by the OS.
The main disadvantage of 64-bit architectures is that relative to 32-bit architectures the same data occupies more space in memory (due to swollen pointers and possibly other types and alignment padding). This increases the memory requirements of a given process and can have implications for efficient processor cache utilization. Maintaining a partial 32-bit model is one way to handle this and is in general reasonably effective. In fact, the highly performance-oriented z/OS operating system takes this approach currently, requiring program code to reside in any number of 32-bit address spaces while data objects can (optionally) reside in 64-bit regions.
Currently, most commercial software is built as 32-bit code, not 64-bit code, so it can't take advantage of the larger 64-bit address space or wider 64-bit registers and data paths on 64-bit processors, or, on x86 processors, the additional registers in 64-bit mode. However, users of free or open source operating systems have been able to use exclusive 64-bit computing environments for years. Not all such applications require a large address space or manipulate 64-bit data items, so they wouldn't benefit from the larger address space or wider registers and data paths; the main benefit to 64-bit versions of applications that wouldn't benefit from them would be that x86 versions would be able to use more registers.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum