I actually have had the same error too. I don't know the "fix" off hand, but changing the ver# to 0.50 fixes it. I thought maybe there was a dependancy missing with the newer ver, since not everyone has this problem, but I don't have a clue what it could be and the readme doesn't say. A quick look around doesn't show a solution, but I haven't tried that hard.