> I think this was fixed yesterday, the newest cvs should have > fixed this. I've just updated, but I'm still getting the same error. I'm using the 0.79dev branch.