I have tried to get SP2 to install on 3683 and 3718, but with no success. I tried to slipstream + do a manual install. Does anyone want to make this a project? I think this would be great. It does sound very unlikely, but we have some great minds here and i think we could make some great progress.

I know someone who did manage to make SP2 install on 3718. Unsurprisingly, 3718 became Windows XP SP2 (not like, pretty much became).

You can't really change 3718 to the extent that SP2 changes it, and hope that it will still retain it's Longhorn parts. You compare XP without a service pack, and an up to date XP, and it is so different.

Right, I just like to have .NET framework installed, Security Center, and the improved wireless management.

The XP Service packs are meant for XP not longhorn builds.

If you apply it, most of the files are changed and longhorn doesnt boot anymore or will look like XP.

If you like to have security center, go to XP it self, alpha/beta's are meant for testing, not using it daily.

In that time frame, the longhorn builds were without a SP.

Well, .Nets up to 2 work on 3718 anyway, we're working on the .net 3.0 and 3.5 as the protoPlex team. Security Center isn't really important as far as I am concerned, but I would like the improved wireless support on 3718. I'll see what can be done about that

cant you extract a service pack 2 and create installers for the apps that you want? the wireles update would be good as a stand alone installer.

I'm thinking about doing another project one day after my Windows Neptune one. I've swapped and changed my mind about what OS to do many times, but i think Longhorn would be the most exciting. There has been plenty of longhorn projects in the past and i bet plenty to come in future... so i'm happy to help out if i'm needed. Who am i? the guy who got a heck of a lot of W2K SP4 into the Alpha1 version of my Windows Neptune project called Neptune Refined

I have a feeling you might be in demand in that case. I'm always looking for people to help update 3718's functionality

I'll PM you if I need you, and I also generally get my way into a lot of other Longhorn projects now days, I'll be ready to recommend you if the job sounds suited to you

No worries, just let me know if i'm needed

Hounsell: I have found some tips for you. Check this site: http://www.bold-fortune.com/forums/index.php?showtopic=229

I will quote what it says about Security Center:


If it'll be of any help, don't credit me, credit the guy that made it!

Hmm, I'll try using those files as a starting point, since I plan to create my second image today

hounsell: Yay. But, don't forget to register the Security Center files! After this, it should work, but i don't promise anything. You may need to add service reg entries for Security Center in order for it to work 100%.

I don't know if this would help but i found this post on another forum . " http://www.joejoe.org/forum/index.php?showtopic=14115 "

"This example is for BUILD 4074 Winhec which has .net framework 2.0.31113 in it.

You have to know the exact version string of the dotnetframework "your" Longhorn comes with !

Have a look inside the C:\Windows\Microsoft NET directory to get the version

1. Locate Explorer.exe ( in some builds it is in C:\Windows AND in C:\ - so put the config in all dirs )

2. open notepad and create an empy file called EXPLORER.EXE.CONFIG

Edit that file and paste the following XML inside :

<xml>
<configuration>
<startup>
<supportedRuntime>
</startup>
</configuration>


( again this is only for 4074 .. other LHs have other <supportedRuntime version="v.x.x.xxxxx" )

save it in the same dir as Explorer.exe as Explorer.exe.config.


3. Install Visual C++ 2005 Runtime redist

4. Install Dotnet framework 2.0 redist

5. reboot"

I tried it and it works for 4074 but i haven't tried it on any others.

it works on any Longhorn build which uses built-in dotnet , as long as you figure out the exact versioning that specific build uses, see "C:\windows\Microsoft .net\.." for example to see them versions. Each Framework version has its own folder somewhere there.

the xml schema used tells Windows to always use the new .NET environment, but NOT for explorer.exe, which will use the built-in framework. You can see, every other application that otherwise would be broken can be made to be excluded.

It's just a dirty workaround, but it works.

You forgot to cite this from Joejoe.