When using Windows’ Remote Desktop Connection to access other Windows machines, I don’t like to have it running full screen, as I’m usually working with many other applications on my local computer at the same time. My primary monitor resolution is set to 1680×1050, but with the taskbar and the RDC window border and title bar, I can’t set the RDC resolution to 1280×1024 without having to scroll to see everything. The next step down in the RDC options is 1280×720, which is a bit too disproportionate for me.

Long story short, you can actually set the RDC window to whatever resolution you desire, using a couple of switches for mstsc.exe (the executable for the Remote Desktop Connection application).

Use the /w: switch to set the width, and the /h: switch to set the height. Simple enough, right? The example below would launch the RDC application with the resolution of your RDC window set to 1280×925. Note that the custom resolution won’t show up in the options for your session, but when you connect to your computer of choice, the window will be the size you specified.

• mstsc.exe /w:1280 /h:925

Here’s an interesting tidbit of information that I wasn’t aware of. Apparently your system memory isn’t only limited by your 32-bit operating system. I installed 4GB of RAM into a system the other day and installed Windows 7 64-bit, and found that the System Properties page showed 4GB installed, but only 3GB usable. What gives?

As it turns out, the amount of usable memory can be limited by the chipset, as well as the BIOS. In my case, the Intel 945 chipset only supports a 4GB address space. Since memory on other hardware devices (i.e. video cards) needs to be mapped somewhere in that address space, some of it is reserved, and cannot be used by the operating system.

Now, if your chipset supports more than 4GB of address space, the BIOS still needs to support memory remapping. The memory remapping feature allows for the other hardware devices to use memory addresses above the 4GB limit, thus allowing the operating system to use all 4GB of system memory. I’m assuming that if the chipset supports more than 4GB of address space, then the BIOS should support memory remapping, but you know what happens when you assume.

What’s interesting to note, and makes perfect sense once you think about it, is that if your amount of system memory is equal to the amount of address space supported by your chipset, then your operating system will never be able to use all of the system memory. Again, this is because of the reserved address space for other hardware in the system.

Microsoft’s knowledge base article #929605 has a good explanation of the requirements for making 4GB or more available to the operating system.