Eclipse Community

Hello Everyone,
I am currently making planning out a project to create a custom iso for Windows XP.

Here are the general ideas of what to do for this iso.

• Add Royale and other popular custom visual styles
• Keep Windows Movie Maker
• Integrate USP4 and any other post-SP3, POSReady2009, and post-EOS updates.
• Redesign Welcome Screen, Boot Screen, and any other resources.
• Ship iso with Snappy Driver Installer
• Create Program that Downloads and Installs Software like Office, etc.

If you are interested in contributing to this project, feel free to reply to this thread.

A lot of this has been done before, though it is worth me pointing out something: POSReady 2009 updates past a certain Patch Tuesday which I can't remember required SSE2 support on the processor, so if you're looking to target XP RTM-era hardware with this package you'd have to provide an ISO without the updates from then on too and get someone with such an old processor (Pentium 3 or Pentium M most likely) to check it out for you. These people are likely in the minority but then again, NM27 SSE is pretty well-used by the XP/2K circle so maybe I'm wrong!

August 2018 would be the first with incompatible updates.

Pentium Ms have SSE2, but I do have a Pentium III desktop where I quickly noticed SSE2 instructions being called by a certain usp10.dll from W7 (scrolling over folder/file icons in a standard explorer window). Athlon XP users should also be a big help, but July 2018 and earlier should be good for XP.

I made a rough list of every (published) update that is incompatible with SSE-only machines. I should compile and share that. And also, figure out the same for systems without SSE.

That would be cool.

Maybe an additional set of service packs catering towards the post-EOS (POSReady 2009) would be a nice plan at this point - rather than integrating them into an ISO - once the list is compiled, y'know... and particularly a 'revised' SP4 for those who really don't want to be installing .NET/IE8/WMP11 within a Service Pack, as that's not how M$ distributed the original SPs either, which is my main gripe about using that package... I'd rather install them after all OS-level security updates and to be fair it's more or less up to the user's jurisdiction too, so yeah.

They'd need to, as we basically just suggested in this thread, be split into separate packs depending on processor architecture, merely to save people downloading more than what they need unless some sort of 'check' can be implemented, but then again bandwidth saving is bandwidth saving on the user's end. we shouldn't treat everyone like a social media guzzling Chrome user

Now that know that post-sp3 is incompatible with sse, I will create two versions, one for old non-sse machines, and one for newer machines.