Archive: February, 2009

Windows Vista

Vista got a lot of things right. It also got a few things wrong. The naggy UAC “are you sure you want to do this” prompts is one example. Another annoyance is the sudden dialog that interrupts what you’re doing to tell you that less than 25% of your RAM is free. This warning would probably be warranted and helpful on systems with a small amount of RAM, but on mine 25% free memory is hardly anything to worry about – it means I have at least 1 GB of memory left.

Annoying Memory Prompt #1

Annoying Prompt #2

Fortunately, like most things, there’s a fix.

  1. Open the registry editor. (Click the Windows orb, type “regedit”, and hit enter.)
  2. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WDI\DiagnosticModules\.
  3. Export the following folders. This is your backup in case something goes wrong.
    {5EE64AFB-398D-4edb-AF71-3B830219ABF7}
    {45DE1EA9-10BC-4f96-9B21-4B6B83DBF476}
    {C0F51D84-11B9-4e74-B083-99F11BA2DB0A}
  4. Take ownership of the each folder mentioned in step 3. (You can take ownership by right clicking the folder and then hitting permissions. Click the advanced button and change owner to your user. Click OK and then give full control to your user group. Hit OK again.)
  5. Delete the folders from step 3.
  6. Reboot and enjoy.

Update: After doing the above steps, you should know that once memory runs out, it is out. You will have no warning. Once your memory gets maxed out, programs will behave very erratic and suddenly crash without warning. I’ve decided that this side effect can be just as annoying as the popups. If you consistently push your machine’s memory to its limits, you should think twice about disabling the low memory messages. Having said that, I still prefer using my machine without Vista’s nagginess.

I began having problems with the Axialis icon editing toolbar in Visual Studio a few weeks ago. It would appear as a short, empty, ugly little toolbar within Visual Studio. I would remove it, even delete it out of Visual Studio, and it still hung around and appeared there every time I started up. Fortunately for me, this problem has a simple fix.

If you’re using a x86 machine, edit the following within the registry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\AddIns\IconWorkshopAddin.Connect
Set value CommandPreload to 0×00000000 (0).

If you’re using a x64 machine, edit the following within the registry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\AddIns\IconWorkshopAddin.Connect
Set value CommandPreload to 0×00000000 (0).

References:

http://www.axialis.com/forum/viewtopic.php?f=4&t=2179