Tal Kain

(NOTE: This is a post that I made on March 4, 2012 that I re-post on this blog after restoring it using archive.org ) ---------------------------------------------------------------------------------------------------------- Not so long ago I decided to buy myself a new computer (since my old one could handle the pressure), I bought myself two hard drives: OCZ Vertex2 60GB Western Digital Caviar Blue (1TB) The SSD for the operating system and the Caviar Blue for all my data. I installed my Windows 7 Ultimate edition (with no SP1), Visual Studio, Office and updated them all using Windows Update. After doing so, I was amazed to find out that I had only 20GB left on my SSD drive – bummer… In order to find out what is taking me so much space I used WinDirStat ( http://windirstat.info ) and find out that my C:\WINDOWS\Installer folder took almost 6GB of my expensive SSD space! After searching the web for a while I found out about Mark Russinovich’s tool called "Juncti

After installing  BinDiff  and running the application for the first time on my Windows 7 x64 machine, I tried comparing two different binaries but got an error in the middle of the process: Can't start disassembler. Please set correct path in the main settings first The solution for this error is very simple: While installing BinDiff, the installation process asks for the installation path of IDA. The default path (on x64 machine) would be C:\Program Files (x86)\IDA\. This is not always correct. At my case the installation was at C:\Program Files (x86)\IDA 6.3\. Moving the path inside BinDiff will not be sufficient since part of BinDiff's files are still on the old directory. Easiest way to fix it (or by doing it in advance): Uninstall BinDiff and install it while pointing to the correct IDA's path. -Tal

While trying to install the Python's  PIL  package on my Windows 7 machine using  pip  I came across this error: Error: Unable to find vcvarsall.bat Although I had Visual Studio 2010 installed, and made sure the batch file exists and the batch file creates the compilation environment correctly, I still got this error. Googling the issue brought this question  with this specific  solution . The short answer (credits to  fmuecke ) is to point the environment variable  VS90COMNTOOLS to the value of   VS100COMNTOOLS . SET VS90COMNTOOLS=%VS100COMNTOOLS% This solved the issue. -Tal