This post was published 2 years 5 months 20 days ago. So some of the links may be broken and the content may not be applicable any more.How easy it is to assume that the user would’ve standard command window configuration? As seen in the screen-shot above, I ran a tool from Windows DDK (the tool ironically is called LooksGood) and it changed my cmd window color scheme to what it assumed looks good ![]()
This used to be a common problem when implementing TSRs in the days of yore. And, one normally took care to store the original forecolor and backcolor of the user’s DOS screen.
I wonder how many of the new programmers who are now using ConsoleColor and Console.ForeColor might have even heard of TSRs let aside building one.
Anyway, this slipped as part of a tool built by Microsoft is the other irony
But to do justice to the developer, it is just a tool to assist in development of a printer driver. And, the intended audience is also quite limited. After all, how many people in this world would run a tool to compare the output of a Raster Image Processor (RIP) to a known good source? Unless of course you are implementing an XPS printer!
( http://blogs.msdn.com/xps/archive/2006/06/02/614795.aspx)
If you are looking at customizing your cmd window, try the following two links…
Using Consolas as the Windows Console Font
Related posts:
