4gb in xp32?
- Thread starter snowdog
- Start date
primarily a 32-bit o/s issue. you can add switches to the bios, like /3GB /PAE to make more available to apps (which are linked with /LARGEADDRESSAWARE flags) - otherwise the o/s grabs as much as it can when it sees the 4GB pool.
even the 64-bit o/s tries to maximise its share, the real advantage is that 64-bit apps are not ram limited per process.
btw, if you edit boot.ini to add the switches, add a completely new line so that you still have your original boot, and a new one with the switches added. This way if something fouls up, you can boot with the old settings and edit out your mods. best of luck.
even the 64-bit o/s tries to maximise its share, the real advantage is that 64-bit apps are not ram limited per process.
btw, if you edit boot.ini to add the switches, add a completely new line so that you still have your original boot, and a new one with the switches added. This way if something fouls up, you can boot with the old settings and edit out your mods. best of luck.
You won't actually see more than 3GB. The 4GB are there, but the o/s hoards a lot more above 2GB, the 2.8-3.2GB are available in user mode.
Even then, apps that are not linked with /LARGEADDRESSAWARE cannot reference more than 2GB of address space.
If you're seeing 3GB+ then the memory is installed correctly, and available. Just not necessarily available to you. If you write your own software you can add the link switch above to address more ram, or if you're a .net junkie, you need to get your hands on the editbin.exe cmdline to add the flag to the app headers.
[edit] xp-sp2 may already address the boot.ini switches (depending on the hotfixes installed) so try permutations, and test your system [/edit]
Even then, apps that are not linked with /LARGEADDRESSAWARE cannot reference more than 2GB of address space.
If you're seeing 3GB+ then the memory is installed correctly, and available. Just not necessarily available to you. If you write your own software you can add the link switch above to address more ram, or if you're a .net junkie, you need to get your hands on the editbin.exe cmdline to add the flag to the app headers.
[edit] xp-sp2 may already address the boot.ini switches (depending on the hotfixes installed) so try permutations, and test your system
[/edit]Hmm you are confusing me, can you please repeat what you said in easy english, im not english and just 16, havign trouble understanding what u mean.
What tags should i add to my boot.ini and what would the result be, at the moment i can see 3.12 gigs of RAM in OS.
Atm this is my OS tag, how would it look like after addign the by you suggested tags?
multi(0)disk(0)rdisk(0)partition(1)\WININT="Microsoft Windows XP Professional Intel x86" /fastdetect /usepmtimer /NoExecute=OptIn /KERNEL=kernel1.exe
What tags should i add to my boot.ini and what would the result be, at the moment i can see 3.12 gigs of RAM in OS.
Atm this is my OS tag, how would it look like after addign the by you suggested tags?
multi(0)disk(0)rdisk(0)partition(1)\WININT="Microsoft Windows XP Professional Intel x86" /fastdetect /usepmtimer /NoExecute=OptIn /KERNEL=kernel1.exe
snowdog said:
Should be:
multi(0)disk(0)rdisk(0)partition(1)\WININT="Microsoft Windows XP Professional Intel x86" /fastdetect /usepmtimer /NoExecute=OptIn /KERNEL=kernel1.exe
multi(0)disk(0)rdisk(0)partition(1)\WININT="Microsoft Windows XP Professional Intel x86" /fastdetect /usepmtimer /NoExecute=OptIn /KERNEL=kernel1.exe /3GB /PAE
Having the two lines will allow you to fall back to a last known good state if the switches cause corruption.