Maximum memory for XP (32-bit)?
Scooby Regular
iTrader: (6)
Joined: Sep 2004
Posts: 14,661
Likes: 5
From: On a small Island near France
Scooby Regular
iTrader: (6)
Joined: Sep 2004
Posts: 14,661
Likes: 5
From: On a small Island near France
Trending Topics
Has to be a way
Back in the day...DOS could only "see" 640k. To see the rest of the RAM you had to load the "HIMEM" driver so that it could address the "upper" area memory..(edit: or was that EMM386
)
Think of it as splitting a large hard disk into two partitions as acting like two logical drives. (ok its nothing like that, but its the best lamens I could think of
)
Back in the day...DOS could only "see" 640k. To see the rest of the RAM you had to load the "HIMEM" driver so that it could address the "upper" area memory..(edit: or was that EMM386
)Think of it as splitting a large hard disk into two partitions as acting like two logical drives. (ok its nothing like that, but its the best lamens I could think of
)
Last edited by Shark Man; May 16, 2008 at 12:58 AM.
IIRC our VM's in uni can see 3.75 gig of RAM (2k3 SP2 AMD CPU's)
My home machine: XP will see 2.93 without memory mapping and 2 with it on, Vista 64 with memory mapping will then see the 4 gig however
My home machine: XP will see 2.93 without memory mapping and 2 with it on, Vista 64 with memory mapping will then see the 4 gig however
Guest
Posts: n/a
32 bit MEANS 2 to the power of 32 - go work it out. It's the maximum address space that ANY 32 bit operating system can see
XP will say it can see 3 and a bit Gb the rest is memory mapped. (graphics cards and the like) To be able to USE more memory you have to go to 64 bit.
However after all that - the extra overhead of managing that memory means that there is a slight performance slow-down. The sweet spot for performance (i.e. gaming) is presently 4Gb.
Oh the 'registry hack' your friend is talking about is adding the /3GB parameter in the boot.ini file.
XP will say it can see 3 and a bit Gb the rest is memory mapped. (graphics cards and the like) To be able to USE more memory you have to go to 64 bit.
However after all that - the extra overhead of managing that memory means that there is a slight performance slow-down. The sweet spot for performance (i.e. gaming) is presently 4Gb.
Oh the 'registry hack' your friend is talking about is adding the /3GB parameter in the boot.ini file.
32 bit MEANS 2 to the power of 32 - go work it out. It's the maximum address space that ANY 32 bit operating system can see
XP will say it can see 3 and a bit Gb the rest is memory mapped. (graphics cards and the like) To be able to USE more memory you have to go to 64 bit.
However after all that - the extra overhead of managing that memory means that there is a slight performance slow-down. The sweet spot for performance (i.e. gaming) is presently 4Gb.
Oh the 'registry hack' your friend is talking about is adding the /3GB parameter in the boot.ini file.
XP will say it can see 3 and a bit Gb the rest is memory mapped. (graphics cards and the like) To be able to USE more memory you have to go to 64 bit.
However after all that - the extra overhead of managing that memory means that there is a slight performance slow-down. The sweet spot for performance (i.e. gaming) is presently 4Gb.
Oh the 'registry hack' your friend is talking about is adding the /3GB parameter in the boot.ini file.
Scrap that... XP can use 4gb (Technet) with /PAE switch on the boot.ini or with the /3GB switch can see 3gb with 1gb for main kernal process (usual is 50/50 split) Thats if you have 4gb installed.
Hope that helps!
Thread
Thread Starter
Forum
Replies
Last Post
Pro-Line Motorsport
Car Parts For Sale
2
Sep 29, 2015 07:36 PM
andy97
Computer & Technology Related
12
Sep 16, 2015 08:07 PM





