Windows XP SP1 + Server 2003 source code has apparently leaked - WARNING ! Your system have been encrypted by Rensenware !

  • 🔧 Actively working on site again.
Here's hoping this source ends up in the hands of the ReactOS development team.

That'd actually be very bad, if Microsoft can prove ReactOS' code is in any way derivative of WinXPs code it'd open the door for them being reamed by Microsofts legal team. I think they tried in the past. You can be sure they'll watch like Hawks if anything of this leak appears in ReactOS.
 
All right, I got my hands on the files, and everyone here has been missing the REAL scoop:
THE SOURCE CODE TO SOLITAIRE
NT\shell\osshell\games\sol

Hearts and the old Windows 3.x Reversi are also under NT\shell\osshell\games
And a number of the Entertainment Pack games (including Minesweeper) are under NT\shell\osshell\ep

dooflop isn't anywhere to be found, which is the other thing I'm sure everyone wanted to know.

A copy of the Hungarian Notation standard from 1988 is at NT\inetsrv\iis\svcs\cmp\doc\hungar.doc

From Freecell:

C:
        //
        // Caution:
        //    This shuffle algorithm has been published to people all around. The intention
        //    was to let people track the games by game numbers. So far all the games between
        //    1 and 32767 except one have been proved to have a winning solution. Do not change
        //    the shuffling algorithm else you will incur the wrath of people who have invested
        //    a huge amount of time solving these games.
        //

Do people really go one-by-one and try to win every Freecell game? :lol: That's some dedicated autism.
 
Last edited:
Here's hoping this source ends up in the hands of the ReactOS development team.
They are already paranoid enough due to NT 4 leaks, which partly explains slowness of their progress. And even then there are enough copyvio accusations on them. If anything, they will have even more headache.

At least we can hope for OpenNT 5.1.
 
Last edited:
Did any of you really use XP? RTM/SP1 was a piece of shit.

My understanding is if you're a big enough client Microsoft will give you access to sources so you can make sure your 30 year old critical app still runs. So yes if you hack someone big like Nintendo there is a chance you'll scoop up Windows too.

But why would anyone still be holding on to SP1 from 2002? That points to it being an old hack that's finally been leaked.
 
Nice.

It'll probably take some time, but I'd love to see a modern day XP that's fully compatible with all modern standards and games. Plus all the removal of the tracking shit MS has put in to Windows 10.

Give me a open source fork that is continually updated to fix flaws and bugs and I'll strongly consider switching or at least dual booting.
 
Nice.

It'll probably take some time, but I'd love to see a modern day XP that's fully compatible with all modern standards and games. Plus all the removal of the tracking shit MS has put in to Windows 10.

Give me a open source fork that is continually updated to fix flaws and bugs and I'll strongly consider switching or at least dual booting.

It's illegal to publish changes made to it though, unless Microsoft allows it, something I doubt quite a bit.
 
It's illegal to publish changes made to it though, unless Microsoft allows it, something I doubt quite a bit.

Offically, sure.

But the underground scene is going to run with this leak.
 
The problem with using XP is that there's no drivers for modern hardware, the driver model changed dramatically with Vista and bad drivers . They could maybe graft some monstrosity to it that kind of works but I get the feeling that it would make Linux in the 90's seem like driver heaven.

Depends, a lot of general drivers got churned out after Vista. It'll take a bit work, but it is conceivable that these could be grafted onto a fork of XP if some group runs with this leak.
 
ReactOS isn't gonna use any of this shit. They do all their dev in a clean room environment. Sp if they use even a line of code from this or any other leak, MS will sue. I think they did like in the 2000s over the nt leak and react was able to prove they didn't use any leaks for their development.
 
ReactOS isn't gonna use any of this shit. They do all their dev in a clean room environment. Sp if they use even a line of code from this or any other leak, MS will sue. I think they did like in the 2000s over the nt leak and react was able to prove they didn't use any leaks for their development.
this subject has come up a lot in the last year whenever some big ass software leak gets dumped online, and yes obviously reactos and emulators like dolphin are clean-room projects. i'd imagine that they're absolutely going to look through this shit and take notes (and microsoft would have an incredibly hard time proving it), they're just not going to directly ctrl+c/ctrl+v lines of confidential ms code into .c files because i doubt any of these projects are that braindead
 
So, can we get a modern windows xp build now. frankly would love to see people build on windows xp and make a whole new freeware windows os(be it still be x32)
 
Here's hoping this source ends up in the hands of the ReactOS development team.
Yeah, directly incorporating stolen code into your open source product is a really great idea.

It seems like even using the source in the 'dirty' part of a clean-room reverse engineering operation could be problematic (as opposed to using technical documents and disassembled code).. it certainly would seem to lead you towards writing pseudocode for every function you were describing, rather than describing its operation.
 
isn't this a potential security problem knowing microsoft's general incompetence? I was under the impression that the reason they don't release source code of old operating systems is because they basically just kept building on top of the old kernel? Or is that just Vista through 10?
 
There's a bunch of strange unreleased themes that look like macos and screenshots of windows neptune.
There's also the sources for paint and the maze screensaver.

Shit's getting good.
 
Back