I have been wanting to get the use of dig on Windows 7 for awhile but hadn’t taken the time to do so until now. The problem is nslookup is not as helpful in terms of TTL of zone files, etc. and while you can accomplish your tasks with nslookup using dig makes life much easier on Windows 7 when troubleshooting DNS type issues. The other night I was in the middle of a time critical launch of a new web cluster and needed dig on the Windows 7 laptop I was working on so I decided to get it working while I was waiting for some data to transfer. I actually had slipped on setting the TTL, which was for a single sub domain that was part of the transfer, from a TTL of a entire day (86400 seconds) to a TTL of one hour (3600 seconds). Anyhow below is more information on installing dig on a Windows 7 computer.
Typically when I need to use tshark I do so on a Linux server however there are times where it is convenient to have tshark available on my Windows 7 laptop. The TShark application is installed with Wireshark so installing TShark is very easy using the Wireshark GUI intsaller on Windows. One thing that makes tshark more useful is adding the tshark.exe executable to your PATH on Windows so you can open a command prompt and use TShark from any directory. Follow the directions below to first install Wireshark and then to add the directory that includes tshark.exe to your Windows 7 PATH.
I have been using Hashcat and oclHashcat a lot in recent weeks but have been limited to primarily using it on Linux servers so I decided to give it a shot on a couple Windows machines. Below I describe how I got oclHashcat operational on Windows 7 Ultimate 32-Bit on a desktop computer with a NVIDIA 9600GT GPU as well as operational on a Windows 7 Ultimate 64-Bit laptop with NVIDIA 9400G M GPU and a NVIDIA G210M GPU. Below is information on what needs to be done to get oclHashcat working on Windows 7.
If you are new to WinDbg (The Windows Debugger) like I am then you might struggle with some of the initial configuration items. I would suggest you do your best to get through the initial configuration issues so you can troubleshoot your Crash Dump files to analyze the issues on your computer. So far I am really happy with Windows 7 Ultimate 64-Bit though I have had multiple BSOD’s (Blue Screens of Death) which are frustrating. I am now doing what I can to get down to the bottom of each of the crashes so I can do whatever it takes to minimize any crashes and continue using Windows 7. Follow the directions below to configure the path to Symbols needed by the Windows Debugger (WinDbg).
Modifying a users PATH variable in Windows Vista is easy. You may want to modify the PATH for a user if you have an executable located in a directory that is not already in the default Path. One example of this is if you install cygwin to have Unix/Linux style commands on Windows you would want to add C:\cygwin\bin to your user Path variable.
Follow the directions below to modify the user Path system variable: