![]() | |
|
Welcome to the ABXZone Computer Forums forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #16 |
| Yes, Yellowbeard ![]() Join Date: Oct 2002 Location: Metro Atlanta, GA.
Posts: 2,626
| Tech ARP - Where The Best In Technology Gather I'm not sure what happened when you enabled this setting in your bios but, it has absolutely nothing at all to do with how much memory your system shows, in the OS or in the bios. This setting also absolutely cannot force XP to use more memory. And, the original poster has already stated that he can "see" 4gb of memory in the bios and when in Windows Sisoft Sandra shows the 4gb. So, detecting the memory is not the question here. It appears that the OP here actually wants to use the memory he bought, not just look at it.
__________________ CORSAIR TECH SUPPORT |
| (Offline) | |
| | #17 |
| Registered User Join Date: Jan 2005
Posts: 1,239
| The biggest problem besides the ignorance of the “issue” is the select words and even statements used. This is not a problem with Windows, Linux, and soon OS X. It is not a problem of utilization for the memory is in use as it should be. It is not even a limitation for it is not preventative. On top of this making general statements concerning BIOS options for the PCI hole is not recommended due to the necessary stepping(s) required for proper change of the MTRR's when the PCI hole remapping has been enabled. Telling a user to look for options and not understanding that it can vary (PCI hole “recovered” memory) not just because of the CPU, but due to everything that is use in the very system. See what is not understood most of all is the fact that what you have enabled, installed, and enumerated in your system takes up memory. From 0x00000000 to 0xFFFFFFFF the memory is mapped for a video card, ACPI, BIOS, etc. But disabling devices will NOT return it either. This is the range in which the device places its data and resides to be communicated with. The range is meant for a many a devices which is under some strain due to limited space in some mapped ranges. However, not having sometimes particular hardware (PCIe take up 256MB and this does not include alias mapped space!) or changing the PCI mapped amount with AGP aperture can reduce the memory hole somewhat. The best I can recommend is reading an Intel motherboard manual. In the monolithic mapped space you will see the graphical representation of how memory has been mapped. I want to write a better explanation but I just do not have the time. Maybe after Christmas I can and shall. But at least with the information presented in the manual I link here I think it can finally be understood: ftp://download.intel.com/design/moth...D7364501US.pdf page 49, section 2.1.1 Addressable Memeory |
| (Offline) | |
| | #18 | |
| Registered User Join Date: Aug 2004 Location: Sidney, OHIO
Posts: 246
| Quote:
__________________ | |
| (Offline) | |
| | #19 |
| Registered User Join Date: Jan 2005
Posts: 1,239
| This has shiny pictures and does the work for me, enjoy: Understanding Address Spaces and the 4GB Limit - [H]ard|Forum |
| (Offline) | |
![]() |
| Thread Tools | |
| Display Modes | |
| |