There are two main groups of parameters that deal with two different types of problem that occur with expanded memory. The first group concerns the position of the page frame. As already discussed, expanded memory works by swapping blocks of memory in and out of a page frame. In the case of LIM 3.2 this page frame has to be a single 64KByte area and the problem is finding such a large free area in the memory map. It is always possible to place the page frame in conventional memory, but this results in a loss of 64 KBytes to applications. Normally it is preferable to find a free 64KByte region in the Upper Memory Area or UMA. If the machine is reasonably normal EMM386 will find such a free space automatically and simply report the address that it is using during system startup. However, it can get it wrong in two ways. If can fail to find a 64KByte area when one actually exists, and it can mistakenly use the first area it finds only to discover that it isn’t actually free. In both cases the solution is to specify the location of the page frame manually. You can do this in two different, but entirely equivalent, ways by adding: There are two main groups of parameters
that deal with two different types of problem that occur with expanded memory. The first group concerns the position of the page frame. As already discussed, expanded memory works by swapping blocks of memory in and out of a page frame. In the case of LIM 3.2 this page frame has to be a single 64KByte area and the problem is finding such a large free area in the memory map. It is always possible to place the page frame in conventional memory, but this results in a loss of 64 KBytes to applications. Normally it is preferable to find a free 64KByte region in the Upper Memory Area or UMA. If the machine is reasonably normal EMM386 will find such a free space automatically and simply report the address that it is using during system startup. However, it can get it wrong in two ways. If can fail to find a 64KByte area when one actually exists, and it can mistakenly use the first area it finds only to discover that it isn’t actually free. In both cases the solution is to specify the location of the page frame manually. You can do this in two different, but entirely equivalent, ways by adding:
0 Komentar untuk "Cloud base hostgetor hosting"