nt5src

Better in which way? It doesn't seem like the RNG is much of a bottleneck[0]. So this code is just more complicated than the original[1] IMO. It is also most likely more costly by involving a bunch of extra divs, logs and (for XP-level HW) floating points, though admittedly the bottleneck on XP-level HW was most likely still the disk. Trying to best Windows devs on performance becomes almost comical if you read the comment for the RtlRandomEx: it is faster than RtlRandom() since it saves one multiplication, one addition and one modulus operation. This almost doubles the performance since it halves the number of clocks even on a pipelined Integer Unit such as the P6/ia64 processors i.e. ~ 52% perf gain. [0]: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b... [1]: https://github.com/tongzx/nt5src/blob/daad8a087a4e7

It doesn't: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b...

For those interested, here's the actual code Chen talks about: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b...

Something the tweet doesn't mention is that the leak may have come from Intel: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b...

> https://github.com/tongzx/nt5src/blob/master/Source/XPSP1/NT... > It is based on the SpiderSTREAMS source, stremul\msgsrvr.c. There's some special history.

> Windows XP/7's video modesetting logic is a bit mysterious. It may try to set a incompatible mode using int10h, which will cause flickering or even black screen after transferring control to the legacy OS. I would really love to know more about this. I assume it's this VGA driver: https://github.com/tongzx/nt5src/tree/master/Source/XPSP1/NT...

No need. https://github.com/tongzx/nt5src/tree/daad8a087a4e75422ec96b...

I think he's misremembering about the format part because the UI does have some arbitrary cluster sizes for NTFS: https://github.com/lianthony/NT4.0/blob/b4a8d373d8a082db6758... That code still seemed to be around in (some versions of) XP: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b... As for the ZIP support, I can't find the source code for ZIP folders specifically. There's this excerpt from another company (Schlumberger Technology Corp.): https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b... which was added in 1996 if the comments are to be believed.

Help yourself: https://github.com/tongzx/nt5src/blob/daad8a087a4e75422ec96b...

Go likes to ignore edge cases ("all file names are UTF-8 and if they aren't then we'll just pretend they are") to make it easier to write code, so I'm not very surprised that it got caught in a POSIX related crash here. It's hard to tell if Microsoft altered the source code since, but the leaked XP source code (https://github.com/tongzx/nt5src/blob/master/Source/XPSP1/NT...) doesn't seem to do any getenv() calls for DNS lookups. The specific bug that started all this nonsense only triggers on (specific) Unix implementations. Unfortunately, Go opts to call the POSIX methods rather than GetEnvironmentVariable/SetEnvironmentVariable on Windows, so I suppose it's still possible that somewhere in the chain this bug gets triggered by Go code.

> Is there any leaked Microsoft code on GitHub? There seems to be. Google 'windows nt source code leak github': https://www.google.com/search?q=windows+nt+source+code+leak+... First search results: Windows NT 4.0: > https://github.com/lianthony/NT4.0 > https://github.com/ZoloZiak/WinNT4 Windows XP: > https://github.com/tongzx/nt5src > https://github.com/onein528/NT5.1