Virtualdub problems :(

Locked
User avatar
Zarxrax
Joined: Sun Apr 01, 2001 6:37 pm
Contact:
Org Profile

Post by Zarxrax » Thu Apr 01, 2004 9:57 pm

sysKin wrote: PS. windows doesn't support more than 2GB of memory, so your physical ram + virtual ram shouldn't go beyond that, anything beyond 2gb will just be wasted.
I'm pretty sure that's incorrect, unless I misunderstand this: http://www.microsoft.com/whdc/hwdev/pla ... AEmem.mspx

User avatar
Kalium
Sir Bugsalot
Joined: Fri Oct 03, 2003 11:17 pm
Location: Plymouth, Michigan
Org Profile

Post by Kalium » Thu Apr 01, 2004 10:05 pm

Zarxrax wrote:
sysKin wrote: PS. windows doesn't support more than 2GB of memory, so your physical ram + virtual ram shouldn't go beyond that, anything beyond 2gb will just be wasted.
I'm pretty sure that's incorrect, unless I misunderstand this: http://www.microsoft.com/whdc/hwdev/pla ... AEmem.mspx
M$ wrote:The /3GB switch allocates 3 GB of virtual address space to an application that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process header. This switch allows applications to address 1 GB of additional virtual address space above 2 GB.

The virtual address space of processes and applications is still limited to 2 GB, unless the /3GB switch is used in the Boot.ini file. The following example shows how to add the /3GB parameter in the Boot.ini file to enable application memory tuning:
IOW, unless you want to screw with your boot.ini, it's still an upper bound of 2 GB on virtual RAM. Even then, the bound goes up to 3 GB.

Just clearing the air a bit.

trythil
is
Joined: Tue Jul 23, 2002 5:54 am
Status: N͋̀͒̆ͣ͋ͤ̍ͮ͌ͭ̔̊͒ͧ̿
Location: N????????????????
Org Profile

Post by trythil » Thu Apr 01, 2004 10:06 pm

Zarxrax wrote:
sysKin wrote: PS. windows doesn't support more than 2GB of memory, so your physical ram + virtual ram shouldn't go beyond that, anything beyond 2gb will just be wasted.
I'm pretty sure that's incorrect, unless I misunderstand this: http://www.microsoft.com/whdc/hwdev/pla ... AEmem.mspx
No, what sysKin said is in line with what WHDC states.

The Windows kernel itself can recognize more than 2GB of RAM, but each application operates in their own 4GB flat address space, the upper 2GB of which is available for application data.

User avatar
Zarxrax
Joined: Sun Apr 01, 2001 6:37 pm
Contact:
Org Profile

Post by Zarxrax » Thu Apr 01, 2004 10:18 pm

Ok I'm really confused now...

If 2gb is all that can be used by applications... what happens with all the rest?

User avatar
Zarxrax
Joined: Sun Apr 01, 2001 6:37 pm
Contact:
Org Profile

Post by Zarxrax » Thu Apr 01, 2004 10:56 pm

Well, I testing it for myself. After hitting 2000MB or memory usage, then attempting to open another program, and waiting about 15 minutes before it let me have control again ;p I discovered that the 2gb barrier does indeed exist.
Guess I'll turn down my swap file some.

Locked

Return to “Video & Audio Help”