ted concurrent execution of processes in memory. If a new process is loaded and there is insufficient main memory an old process is swapped to disk. This swapping process is called virtual memory. Windows 3.1 used virtual memory, but since is was a 16 bit system is didnt use is as effectively as Windows 95. Users of Windows 95 didnt have to worry about conventional, extended, or expanded memorymemory was installed and just used by the system. This made life easier for the user. Windows 95 uses a 32-bit code, which can move data at higher speed than the 16-bit code used by previous versions of Windows (Windows 3.1, 3.11, etc.). As a result, Windows 95 memory management is more efficient, and printing and other tasks finish faster. At least in theory, the system is more stable.It's a fact that Windows 3.1x has nowhere near the memory management capabilities of Windows 95. All Windows 3.1x users have experienced this lack of efficiency when your computers would "hang" or "crash". Although these disasters seemed to happen for no apparent reason, they were often the result of opening and closing programs without periodically exiting Windows 3.1x and restarting your computer. Even if only one program is open at any given time, the mere opening and closing of a program can wreak havoc on memory in Windows 3.1x.Because their is a finite amount of real memory (RAM) in your computer Windows 95 also used a virtual memory scheme to enable all active programs to share this limited resource. Each program is given 4GB of virtual address space. This virtual memory is mapped to the Page Table. The Page Table maps the virtual memory to real RAM memory and that area on your hard disk called the swapfile. The swapfile will not be used until all of RAM is in use. The major difference between Windows 3.x and Windows 95 was that 95 did this much faster and much more efficiently then 3.x.The Page Table is used to keep track of what is in RAM and what has...
