Update: You can use the following registry script to automate this process – just copy/paste the code block below into a text file called “Add Consolas to CMD.reg” and run it:
Windows Registry Editor Version 5.00
RegEdit - Console Fonts
If you’d like to use an alternative console font for CMD.exe in Windows, check out the scoop from Microsoft Support on how to set it up…
The fonts must meet the following criteria to be available in a command session window:
The font must be a fixed-pitch font.
The font cannot be an italic font.
The font cannot have a negative A or C space.
If it is a TrueType font, it must be FF_MODERN.
If it is not a TrueType font, it must be OEM_CHARSET.
Additional criteria for Asian installations:
If it is not a TrueType font, the face name must be “Terminal.”
If it is an Asian TrueType font, it must also be an Asian character set.
In Windows 2000, the installation of Console Fonts is no longer automated. This was done to give the console window greater stability in multilanguage environments. An unsupported work around is available by adding the following font specific entry:
Add a String Value
Data= “Font Name” (without “”)
Droid Sans Mono:
Straight from the Android SDK comes the Droid Sans Mono font, which is quite similar to the DejaVu Sans Mono font listed above. You can grab this from the Android SDK download, or you can get it directly from the damieng blog here: Droid Sans Mono great coding font
This has nagged me for soooo long! I use Winamp, which has its own context menu integration, and I find myself accidentally opening a folder to play in Windows Media Player all the time…
Leave my context menu alone! If you just let it go wild, every program in the world wants to install some option there. Windows Media Player not only puts itself there, but integrates itself throughout the shell. Actually removing this integration is surprisingly easy!
Remove WMP Integration: 1. Click Start
2. Click Run
3. Type in regsvr32 /u wmpshell.dll
4. Click Enter
I haven’t tried using my favorite XP junction tool, NTFS-Link, since I upgraded my home computer to Windows Vista, and I’m a little apprehensive since the filesystem has changed a bit. Nonetheless, if you are still using XP, NTFS-Link is an excellent tool for those of you already familiar with symbolic links via other operating systems, such as Linux.
Luckily, Windows Vista does include a command-line tool for creating symbolic links, similar to “ln” in Linux. However, it’s not quite as straightforward. Here’s the scoop from How-To Geek:
Using the mklink Command
The command that you need to use is mklink, which you’ll use from the command line. Just type it on the command line to see the options:
Creates a symbolic link.
MKLINK [[/D] | [/H] | [/J]] Link Target
/D Creates a directory symbolic link. Default is a file
/H Creates a hard link instead of a symbolic link.
/J Creates a Directory Junction.
Link specifies the new symbolic link name.
Target specifies the path (relative or absolute) that the new link
Update: This application will help you track down which applications are using which ports on Windows – very helpful for debugging if the steps below don’t solve your problem, or if IIS is not the only application answering on port 80: http://winnetstat.zapto.org/
Also, if you don’t specifically need all the features of XAMPP, but would like to run PHP/MySQL applications through IIS, give Web Platform Installer a try. Through WPI, you can choose to install PHP directly within IIS (so that IIS can serve both ASP.NET and PHP applications on port 80, for example) and you can also have a ton of applications installed and configured automatically for you, such as Drupal, WordPress, and Moodle (among many others). However, if you are still looking to run XAMPP specifically, or just run an Apache instance along with IIS, check out the instructions below. Thanks for visiting!
Now that I’ve finally made the leap to install Windows Vista on my home computer, I thought it might be useful to dig through some old (and new) guides to keep Vista from annoying me as much as it did when I first tried it out in beta. Luckily, things are going much more smoothly this time. Here’s a helpful tip from the How-To Geek about how to run a command as an Administrator from the Vista Run box.
FYI: The Run option is not enabled by default on the Start Menu. You’ll either need to open it by using the Win + R key combination or by enabling it through the Taskbar Properties, using the steps below:
Right click on the taskbar, then choose properties.
Once in the “Taskbar and Start Menu Properties” dialog, click the “Start Menu” tab, then click “Customize…”
Scroll down to the “Run command” option, and check it.
Close the dialog.
Now, you’ll have the “Run…” command back in your Start Menu, but it’s worth noting that the newer Vista “Start Search” bar is a lot more versatile than the older “Run…” command. In either case, from “Start Search” or from “Run…”, the following steps will help you to run a command as an administrator (from How-To Geek):
To try this out, go to the run box and type in something (cmd, for example)
Now instead of hitting the Enter key, use Ctrl+Shift + Enter. You will be prompted with the obnoxious User Account Control dialog… but it will then open up a command prompt in Administrator mode.
This seems to be a pretty common problem in Windows Vista, related to invalid/corrupt color profiles – if you’re experiencing this issue, you’ll see a beige color bleeding through the image from the background where a white background should be. Here’s an example (thanks to matthewrowan.spaces.live.com!):
After a little searching for how to change the background color, I found other people with this symptom describing it as an off color, yellow tint, orange or yellowish tinge, beige, cream colored background which, shows through the picture itself, distorts the colours, or bleeds through pictures. In most situations the problem went away in slide show mode. This was an annoying issue, making me avoid looking at pictures whatsoever in Windows Photo Gallery. This wasn’t that much of an issue because I do not use photos or pictures often on my development machine. But before I was going to install Vista on my other computer where I view photos constantly, I needed to ensure that I would not have this issue.