I just noticed this part of your original post.
Could the problem be linked to Python 2.6.2 in particular?
Maybe it is the python version that determines whether
or not the problem is observed?

On Jun 21, 2010, at 2:40 PM, Alex Hall wrote:
>
> someone told me that this seems to happen to random machines and they
> are not sure how to fix it. Until I get this sorted, I cannot start
> helping with development since nothing works after this error, so I
> cannot test any of my changes. Any information would be great.
> Python2.6.2 on win7x64 (32-bit python installed), AMD quad core at
> 3.2GHz with 4gb ram at 800MHz