That had something to do with a particular version of an MS dll, the name of which I cannot remember at the moment. I'll look around some more, and perhaps we'll get lucky and someone will recall the relevant thread - here or wherever it was posted.