The upside of findstr is that it is included with Windows since a long time (at least since Windows XP, later: indeed since Windows ME) and supports a form of regex.
SmallestDotNet – SmallestDotNet.com is a single page site that does one thing. It tells you the smallest, easiest download you’d need to get the .NET Framework on your system.
Even on Mac OS X it is helpful and recommends Mono and on iOS it recommends looking at MonoTouch.
When you have multiple network connections, sometimes you want to prefer one to be used as “default” (i.e. because it has higher speed or lower latency).
Windows already tries to accommodate for that by assigning “metrics” to your network connections. They depend on the kind of network (wired over wireless) and speed of the connection.
To see the current default network routes and their metrics, you use the route print command and filter it with findstr like this:
route print | findstr /C:"Metric" /C:" 0.0.0.0"
The “0.0.0.0” string is to filter out the default routes, and “Metric” includes the header line.
For one of my XP machines, the result is this:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Now, even though both metric are 10, my 192.168.71.1 gateway is much slower than my 192.168.171.1 gateway, so I want to prefer the last one. Read the rest of this entry »
Just in case you need to stay with XP for a while (for instance because you have hardware where the vendor still has no drivers for more modern Windows versions), you might want to block KB2934207 A notification about the end of Windows XP support.
As of March 5th, this “high priority” KB2934207 update installs a notification screen remembering Windows XP will be End of Support at 20140408 (about 2 weeks from now).
If you do keep Windows XP, then make sure you have good protection for it (even watch that closer than you would on more current systems).
Never noticed this file before until I got some trouble with several systems sharing parts of a roaming profile.
The content of my %USERPROFILE%\ntuser.ini file is this: [General]
ExclusionList=AppData\Local;AppData\LocalLow;$Recycle.Bin;Tracing;PrivacIE
[ProfileLoadType]
LastUploadState=Complete
[[The ntuser.ini file is used to set up the user roaming profile components that are not copied to the server.]]