In this episode of Defrag Tools, we geek out on our favorite Command Prompt commands.
where doesn't seem to work in PowerShell.
@jlomax:In PowerShell you have to type where.exe for it to work.
@defrag team, you guys need to spend some time with Jeffrey Snover!
if you really want device manager the use hdwwiz.cpl instead.
I use this to easily check out the SQLSErvr running services and manage storage too.
more like this, very interest in more Windows Internals and Commands.
Win+Pause HYPE! I am constantly trying out various Win+[some other key] combos when I have a few seconds over (loading screens) in hope of finding a new super useful shortcut key like Win+Shift+S. [H] Didn't know about Win+Pause! Thanks a bunch!
qwinsta & rwinsta - I don't use them every day, but probably every month.
This is commands I using and use in Windows 7, 8 and XP.
One of the best "type <file> | findstr [options]". However there is a /A option to findstr where you should be able to specify a color code as defined in "color /?" however I have never seen this work. The Linux guys always rub it in that grep does this automatically. Have you been able to get the /A option to work with findstr?
I've written a tool to specifically store and organize all the command line tools that I use so that I can easily reuse the command. Check it out at https://github.com/simon1tan/TechTools.
The main reason I use 'where' through the PATH is to find the latest, greatest version of Dbghelp.dll, WinDiff, etc. The more SDK's installed, the more versions you might have.
to see how to do a recursive search from anywhere. Don't forget the /T.
The /P for findstr.exe is don't show non-printable results. This avoids seeing compiled/linked files that might match your search string.
I find find.exe useful for streams. I often pipe 'findstr' results to 'find' similarly to how Andrew pipes to 'findstr' repetitively.