Shard Crash
Re: Shard Crash
Its ok Hina Thanks for the update!
-
kellsar wolf
- Journeyman Scribe
- Posts: 29
- Joined: Tue Dec 01, 2009 4:08 pm
- Location: ~KnowsLocation
Re: Shard Crash
yippie kai yay!
-
Orbit Storm
- Legendary Scribe
- Posts: 254
- Joined: Wed Oct 14, 2009 5:02 am
- Contact:
Re: EXCELSIOR DAILY
***Edit:
I agree with Shandy.. but as I originally stated, without knowing the OS, we can't really tell you what to do.. =)
I agree with Shandy.. but as I originally stated, without knowing the OS, we can't really tell you what to do.. =)
Last edited by Orbit Storm on Wed Dec 02, 2009 1:35 pm, edited 1 time in total.
Re: EXCELSIOR DAILY
Their are a few things that could be responsible... The first thing to try is to open Run type msconfig and hit enter.
Under the Boot.ini tab click advanced options, click/tick the box to enable the switch to set max memory (/MAXMEM=) and see what value pops up, if it's NOT the value of your total physical RAM (in MB) then set it to it. (RAM in GB * 1024 = RAM in MB).
I doubt this is the issue, but it is the easiest possibilty to check.
If your running an x32 NT enviroment (Windows XP Professional, Windows Server 2003, Windows NT Server 4.0 Enterprise Edition) you can set the switch /3GB in the boot.ini file after the operating system address, eg:
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="[Your OS]" /3GB
Then edit the server emulator or whatever is demanding more than 1.5GB of memory and place this line in the header:
IMAGE_FILE_LARGE_ADDRESS_AWARE
This should allow the emulator to aquire up to 3GB of memory, leaving 1GB for kernel etc. where previously it was 2GB for user processes and 2GB for kernel and private address space... This only applies to 32bit enviroments though.
Other solutions will likely involve APIs, which gets complicated.
Under the Boot.ini tab click advanced options, click/tick the box to enable the switch to set max memory (/MAXMEM=) and see what value pops up, if it's NOT the value of your total physical RAM (in MB) then set it to it. (RAM in GB * 1024 = RAM in MB).
I doubt this is the issue, but it is the easiest possibilty to check.
If your running an x32 NT enviroment (Windows XP Professional, Windows Server 2003, Windows NT Server 4.0 Enterprise Edition) you can set the switch /3GB in the boot.ini file after the operating system address, eg:
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="[Your OS]" /3GB
Then edit the server emulator or whatever is demanding more than 1.5GB of memory and place this line in the header:
IMAGE_FILE_LARGE_ADDRESS_AWARE
This should allow the emulator to aquire up to 3GB of memory, leaving 1GB for kernel etc. where previously it was 2GB for user processes and 2GB for kernel and private address space... This only applies to 32bit enviroments though.
Other solutions will likely involve APIs, which gets complicated.