What is the "useful" memor limit in server 2k?

[JBruyet]

Hey all,

We purchased a software program from a company a few years ago. That company got bought out and the new company is struggling with supporting the original software (they want us to buy their "new" software but we don't have the $$$ to do it at this time). We are currently struggling with using one of the modules of the software--we use the module and the server takes a memory hit (no changes made;normal data growth?). Once users activate the module paging kicks in, performance drops and users think their workstations are locking up when they're just waiting for the server.

The response from support is put more memory in the server. At this time the server has two gigs of memory. I've been told in the past that Windows 2000 Server can only use two gigs and that putting more memory in just causes random errors. Will Windows 2000 Server see four gigs of memory? And run it error-free? Will it see the additional memory with Registry tweaks? Any help here would be greatly appreciated.

Thanks,

Joe B

 

[dberg35]

Look at the following link.

http://support.microsoft.com/kb/304297

 

[JBruyet]

dberg35,

If I recall correctly from my Windows 2000 Server class (too far back and I can't find my notes) Windows can take four gigs but it can't "effectively use" all four gigs. At one point I thought that there was a Registry tweak to "enable" the rest of the memory but I can't find it. Thus my request here on Tek-Tips for help.

Thanks,

Joe B

 

[dberg35]

There might be a reg crack but I wouldn't recommend it. I think what your refering to is if you installed more than the OS can see then you could use crack to make it see all the memory. What you might want to look at is your Page File size. If it windows default then change it to make it larger and if possible on a different partition than your OS.

 

[victorv]

hi,
I believe that you can run Task Manager and in Process Tab,
see which process use yor memory, and take right conclusions.

About 2/4 GB Memory, 2000 has not the capability that have 2003 and XP to split addressable memory (not just physical, but also swap) of 4GB, instead of 2 for system and 2 for Application, in 3 for Application and 1 for system using qualifier /3GB in boot.ini file (manually or in System Prop/Advanced/Startup and Recovery Settings\Edit).

ciao
vittorio

 

[strongm]

>2000 has not the capability ... /3GB in boot.ini

It does. the /3GB switch was introduced in Windows 2000 Advanced Server. But the application really needs to have been written to take advantage of that properly (using a specific compiler switch)

However, this seems to be a paging issue, which the /PAE switch can theoretically help alleviate. I say theoretically because it ntroduces its own problems. I suggest that the OP investigates documentation on both the /3GB switch and on the /PAE switch to see if either are suitable.