Hi Rob, > The RFC recommends the following: > > o Set the two most significant bits (bits 6 and 7) of the > clock_seq_hi_and_reserved to zero and one, respectively. > > However, I don't see that done in your patch.
Thanks, I missed that. > Have you checked which algorithm recent versions of Windows use and > what bits are set? Yes, they use this version of the algorithm, and have for some time now. I just verified on Win2k. (So does uuidgen on Linux.) UuidCreateSequential may use the old algorithm, I'm not sure. I'll update the patch. It'll still cause intermittent failures in the quartz tests, which I don't believe are truly caused by the change, so perhaps it'll never get in. --Juan
