Comment 4 for bug 256550

Just to confirm, with non-ascii characters in my host name, it does fail in the same location, and the string appears to be in cp1252 encoding.

I'm sure that isn't your encoding on Russian Vista, though, so we would need to figure out what platform function we need to call to find the appropriate encoding of the socket.gethostname() function.

In the worst case, we could always fall back to something that guarantees a mapping for every character (such as iso-8859-1).

For this lock/info file, it isn't 100% critical to be correct, it is just a nicety.