I believe this was a windows problem -- several folk confirmed that it worked OK on unix.

I see. In that case I will be not be in a position to help you solve it. :-)

However, if you can verify that it is a problem with the module (even if only on MSWin32), it would be good to raise that as an issue so that it can be fixed by the maintainers.