Windows   

From OzmoWiki

32-bit 4GB Limit

This works in VMware as well.

C:\>bcdedit /set nx AlwaysOff
The command completed successfully.

C:\>bcdedit /set PAE ForceEnable
The command completed successfully.

C:\>shutdown -r -t 0 -f -c "Enable PAE to remove 4GB RAM limit."

PAE Maximums are defined here

Works on:

• Windows Server 2003, Enterprise/Datacenter Editions
• Windows Server 2008, Enterprise/Datacenter Editions

Virtual Store

Vista Pain In The Neck Rule #1: If you modify or create a program in the Program Files directory, or a program does it for you, Vista will play tricks on you.

This includes:

1. Editing a file yourself, even if you have administrator privileges
2. Any program that writes a data file to the program files directory (unless it’s an installer).
3. Any program that writes configuration or .ini files to the program files directory (unless that program was launched by an installer).

I had modified a file, using Vi, in C:\Program Files\Vim. The file was called vimrc. The modified file contained a version string 20080710. I copied this file to my USB key and see use it at work. When opening the file at work, I noticed there was no version string (what, what, what?!!)

Then, I remembered the whole UAC, and how Vista makes a “shadow” copy. That’s what happens when Vista asks for special permission to continue with the “File Save” or delete. To make a long story short (too late), I found the updated file lurking in: C:\Users\Ozmo\AppData\Local\VirtualStore\Program Files\Vim\vimrc

Lessons Learned To Date

1. If a program file needs to write important data to its own directory, install it somewhere else. I have set up C:\Apps, for this purpose.
2. If you are backing up a program that seems to store its data in its own directory, and you didn’t follow #1 above, don’t count on the backup actually having the right files!
3. If you install a program and it offers to “Run Program Now?” Don’t! Just let the installer quit, and then run the program yourself. Otherwise, you’ll run the risk of the program running with elevated privileges, and creating data and configuration files that cannot be updated later.
4. If you edit anything in the Program Files directory, you’re asking for trouble. Be sure to check the VirtualStore cache.
5. The Virtual Store resides in: C:\Users\<userid>\AppData\Local\VirtualStore\