Windows Vista: The OS About Nothing

M

Mousebaby

Guest
Got 64bit Vista here, but sadly just found out from HP I can't get anymore memory for this computer. It has 4gb. I wanted to double it, they said it could not handle it.
 
Got 64bit Vista here, but sadly just found out from HP I can't get anymore memory for this computer. It has 4gb. I wanted to double it, they said it could not handle it.

In all honesty, I am running VISTA on my 1710 and it is flying with 4GB - it even runs just as fast with 2GB. If I render with Photoshop CS3 is slows down with 2, but not with 4... the typical user will never go this far though.

Not sure about the 64bit OS - but I imagine the memory footprint is not that much more different, so you should be OK with 4GB for the life of your laptop.

Let me know if you want to trade that XPS away for my Optiplex. :lol:
 
M

Mousebaby

Guest
In all honesty, I am running VISTA on my 1710 and it is flying with 4GB - it even runs just as fast with 2GB. If I render with Photoshop CS3 is slows down with 2, but not with 4... the typical user will never go this far though.

Not sure about the 64bit OS - but I imagine the memory footprint is not that much more different, so you should be OK with 4GB for the life of your laptop.

Let me know if you want to trade that XPS away for my Optiplex. :lol:

I don't think so! I got too much money wrapped up in that thing. I have decided to just use it for when we travel. So it will sit in my laptop case and collect dust in the mean time. Its the new computer that run 64bit vista and I was told with the 64 bit the computer uses all the 4GB. If you have regular 32bit vista you only use about 3.2GB of your memory. :shrug: That truly sucks cause try finding 64bit XP its almost impossible! And when you do boy is it overpriced!
 

Floyd2004

-Void-
If you have a 32bit OS you have to add in the video ram also with the system memory to total 4gig.
EX: I have 1gig of video memory so I can only have up to 3gig of system mem.
EX I have 512meg of video memory so I can have up to 3.5gig of system mem.


See it all depends on what you have. On my machine I can only have 3gig though.
 
I don't think so! I got too much money wrapped up in that thing. I have decided to just use it for when we travel. So it will sit in my laptop case and collect dust in the mean time. Its the new computer that run 64bit vista and I was told with the 64 bit the computer uses all the 4GB. If you have regular 32bit vista you only use about 3.2GB of your memory. :shrug: That truly sucks cause try finding 64bit XP its almost impossible! And when you do boy is it overpriced!

Wow - I am looking right now on a 32-bit VISTA platform, with Outlook, IE7, Word, X-Windows emulator and a couple of SSH terminals open I am using just shy of 1.2 GB. :confused:

I would hold on to the XPS and re-load XP or a fresh VISTA, mine at home running VISTA 32-bit, running Outlook, IE7 and word is right around 800MB...
 
M

Mousebaby

Guest
Wow - I am looking right now on a 32-bit VISTA platform, with Outlook, IE7, Word, X-Windows emulator and a couple of SSH terminals open I am using just shy of 1.2 GB. :confused:

I would hold on to the XPS and re-load XP or a fresh VISTA, mine at home running VISTA 32-bit, running Outlook, IE7 and word is right around 800MB...

I think you are misunderstanding what I am saying. In a 32 bit machine it will max out to 3.2GB of RAM if you had everything going all at once. In a 64 bit machine you would max out at 4GB of RAM if you had everything going at once. Only the 64bit machine is able to utilize all 4GB of RAM. Does that make more sense?
 
I think you are misunderstanding what I am saying. In a 32 bit machine it will max out to 3.2GB of RAM if you had everything going all at once. In a 64 bit machine you would max out at 4GB of RAM if you had everything going at once. Only the 64bit machine is able to utilize all 4GB of RAM. Does that make more sense?

I understand what you are saying now... only because of the Kernel change between XP and VISTA and how the Kernel utilizing memory based on what devices it has to work with (video, chipsets, audio controllers, USB and FireWire controllers/devices.) I thought you meant "typical" running footprint. Now I understand, here is a bit more information for you to smoke your mind... :cool:

The 32-bit O/S (regardless if its XP or VISTA) can still addresses the entire 4GB, you only see (say 3.5GB) because if your video adapter has 512MB of memory on board, the O/S must map that 512MB in its first 512MB of resident memory. Graphics memory mapping overwrites resident memory.

Also, other devices that utilize DMA (Direct Memory Access) and drivers loading will also suck up pieces of resident memory. These are little known facts about windows.

Even though you have a 64-bit machine you may or may not be able to utilize the entire 4GB as well - here is a snipit from MSDN on the subject;

For Windows Vista to use all 4 GB of memory on a computer that has 4 GB of memory installed, the computer must meet the following requirements:
• The chipset must support at least 8 GB of address space. Chipsets that have this capability include the following:
• Intel 975X
• Intel P965
• Intel 955X on Socket 775
• Chipsets that support AMD processors that use socket F, socket 940, socket 939, or socket AM2. These chipsets include any AMD socket and CPU combination in which the memory controller resides in the CPU.

• The CPU must support the x64 instruction set. The AMD64 CPU and the Intel EM64T CPU support this instruction set.
• The BIOS must support the memory remapping feature. The memory remapping feature allows for the segment of system memory that was previously overwritten by the Peripheral Component Interconnect (PCI) configuration space to be remapped above the 4 GB address line. This feature must be enabled in the BIOS configuration utility on the computer. View your computer product documentation for instructions that explain how to enable this feature. Many consumer-oriented computers may not support the memory remapping feature. No standard terminology is used in documentation or in BIOS configuration utilities for this feature. Therefore, you may have to read the descriptions of the various BIOS configuration settings that are available to determine whether any of the settings enable the memory remapping feature.
• An x64 (64-bit) version of Windows Vista must be used.
Contact the computer vendor to determine whether your computer meets these requirements.

Note When the physical RAM that is installed on a computer equals the address space that is supported by the chipset, the total system memory that is available to the operating system is always less than the physical RAM that is installed. For example, consider a computer that has an Intel 975X chipset that supports 8 GB of address space. If you install 8 GB of RAM, the system memory that is available to the operating system will be reduced by the PCI configuration requirements. In this scenario, PCI configuration requirements reduce the memory that is available to the operating system by an amount that is between approximately 200 MB and approximately 1 GB. The reduction depends on the configuration.

In theory with todays designs of O/S, not the theoretical addressing limits (below), 64-bit applications running on a 64-bit operating system are allotted 8 TB in virtual memory for user processes and 8 TB for kernel processes which make the virtual memory total equal 16 TB.

Currently, all 64-bit versions of Microsoft operating systems do not use the 16 TB limit, but impose a practical limit on the address space and allow no more than 128 GB of physical memory to be accessed. Now, with 64-bit VISTA, you can address different amount of memory based on the type of VISTA you have;

Home Basic: 8GB
Home Premium: 16GB
Utimate: 128GB +
Business: 128GB +
Enterprise: 128GB +

64-Bit XP goes up to 128GB

Bottom line, 2 to the power of 32 = 4,294,967,296 - we know this as 4GB, the max which any 32-bit O/S can address. 3 flavors of Server 2008 (32-bit) can go up to 64GB of physical memory, but this is using something called PAE which we will NOT get into :lol:

2 to the power of 64 = 1.84467441 × 10^19 (ten to the 19th power) - we know this as 16EB (EXABytes - or 16.8 Million TeraBytes - or 16.8 Trilion GigaBytes), the 64 bit O/S is theoretically capable of addressing this much memory, but currently only go out to about 2TB of physical memory, and only go out to about 8TB in swap space (maybe more)... I am not sure of any O/S going beyond 2 TB of memory today though. :shrug:


Here is some light reading (table) giving you some ideas of where Microsoft is today;
Memory Limits for Windows Releases (Windows)

The 64-bit Architecture mathematically can hit the 16 EB mark, but the O/S vendors do not have the kernels ready to address that much space - I believe their high-water marks for memory addressing is 16TB.
 
Last edited:
Thats alot of Ram... I thought 8gig was insane for a home user!

Today it is! :lol: Maybe not in a few years.

Since we are talkng memory, I just ordered a server here at work - to give you an example of cost...

With 16GB it came out to 11K, to take it to 32GB was only an additional $1200. To go to 64GB was an additional $7400 more than original price, to jump to 128GB was $12,000 more than orig. :faint:
 
M

Mousebaby

Guest
I understand what you are saying now... only because of the Kernel change between XP and VISTA and how the Kernel utilizing memory based on what devices it has to work with (video, chipsets, audio controllers, USB and FireWire controllers/devices.) I thought you meant "typical" running footprint. Now I understand, here is a bit more information for you to smoke your mind... :cool:

The 32-bit O/S (regardless if its XP or VISTA) can still addresses the entire 4GB, you only see (say 3.5GB) because if your video adapter has 512MB of memory on board, the O/S must map that 512MB in its first 512MB of resident memory. Graphics memory mapping overwrites resident memory.

Also, other devices that utilize DMA (Direct Memory Access) and drivers loading will also suck up pieces of resident memory. These are little known facts about windows.

Even though you have a 64-bit machine you may or may not be able to utilize the entire 4GB as well - here is a snipit from MSDN on the subject;



In theory with todays designs of O/S, not the theoretical addressing limits (below), 64-bit applications running on a 64-bit operating system are allotted 8 TB in virtual memory for user processes and 8 TB for kernel processes which make the virtual memory total equal 16 TB.

Currently, all 64-bit versions of Microsoft operating systems do not use the 16 TB limit, but impose a practical limit on the address space and allow no more than 128 GB of physical memory to be accessed. Now, with 64-bit VISTA, you can address different amount of memory based on the type of VISTA you have;

Home Basic: 8GB
Home Premium: 16GB
Utimate: 128GB +
Business: 128GB +
Enterprise: 128GB +

64-Bit XP goes up to 128GB

Bottom line, 2 to the power of 32 = 4,294,967,296 - we know this as 4GB, the max which any 32-bit O/S can address. 3 flavors of Server 2008 (32-bit) can go up to 64GB of physical memory, but this is using something called PAE which we will NOT get into :lol:

2 to the power of 64 = 1.84467441 × 10^19 (ten to the 19th power) - we know this as 16EB (EXABytes - or 16.8 Million TeraBytes - or 16.8 Trilion GigaBytes), the 64 bit O/S is theoretically capable of addressing this much memory, but currently only go out to about 2TB of physical memory, and only go out to about 8TB in swap space (maybe more)... I am not sure of any O/S going beyond 2 TB of memory today though. :shrug:


Here is some light reading (table) giving you some ideas of where Microsoft is today;
Memory Limits for Windows Releases (Windows)

The 64-bit Architecture mathematically can hit the 16 EB mark, but the O/S vendors do not have the kernels ready to address that much space - I believe their high-water marks for memory addressing is 16TB.

OOOOOOOOWWWWWWWWWWW I think I just hears something snap! Oh it was just MY BRAIN!!! :faint:
 
R

RadioPatrol

Guest
Today it is! :lol: Maybe not in a few years.

Since we are talkng memory, I just ordered a server here at work - to give you an example of cost...

With 16GB it came out to 11K, to take it to 32GB was only an additional $1200. To go to 64GB was an additional $7400 more than original price, to jump to 128GB was $12,000 more than orig. :faint:

Is that some new Solaris System ?


I have been drooling over this for 2 yrs ...

Thunder n4250QE (S4985)


The Thunder n4250QE (S4985) offers support for AMD Opteron ™ 8000 Series processors for high-level workstation and serving applications. A true monster platform, the S4985 also supports up to (4) PCI Express x16 slots, a PCI slot, SATA2 with RAID, dual Gigabit and single 10/100 Ethernet port, built-in video, and remote management (IPMI 2.0) option, all in a massive SSI MEB (16" x 13") form factor. Add the M4985 for additional 4P configuration, for a total of (8) processors in all!


:drool:


it now supports 4x 512k L2 Cache/2MB L3 Cache Quad Core Opteron™

for 32 Cores of Processing Goodness .......

talk about a system to run multiple VPC's on ...
 
Last edited by a moderator:
Is that some new Solaris System ?

No, it is for a Linux BEA Web Logic web server of all things. :lol:

These guys wanted two, dual core CPU's - instead of the new quad cores. When I asked "Why in the hell..." they said it was because of licensing BEA Web Logic Server is based on the number of CPU's... Dual Core was 25K, Quad Core was 50K.

This is the price of a Dell PowerEdge 2950 III - 3TB of internal RAID 5...


That board you show looks like it is going to fly. :yay:
 
Top