question for those who've slip-streamed into XP gold disc:
Do you notice that the OOBE at first boot seems to have disappeared?
This happens on xp-home & xp-pro (all oem/vlk/retail types).
OOBE was appearing fine with SP2 on the same discs, and I dont think MS intended to get rid of it.
Either something has changed with SP3 or something wrong with the disc?

According to the new Systems Management Server OOBE policy, the OOBE at first boot is optional, not mandatory, depending on the product key you've used. Microsoft merged Retail and Corporate in the same codebase, like on Vista. So, depending on the key, you've got Retail, VLK, OEM, or whatever.

So yes, Microsoft did intend to get rid of it. In a few months the beta program will be available for all MS Connect users to join and they'll publish there the specs.

And as for the keys, is it more of a white-listed set of PIDs than black-listed? Seems that way...

This post has been edited by prathapml: Aug 11 2007, 06:35 AM

I thought it was nLite bypassing this Nice find

Like I said, we TAP members are supposed to test it before it gets to Connect

Last minute edit: There will be a release of SP2c , a subset of this SP3 v.3180 just for Professional Edition, to be released to manufacturing. It seems Microsoft believes the beta for SP3 will be long and painful, I haven't seen such a measure since NT 4.0 SP6a. Thus, XP SP2c Pro goes RTM in September 2007; the others don't.



I think you all know how it goes with Vista installed without entering a key. This is exactely the same.

This post has been edited by dexter.inside: Aug 11 2007, 09:08 AM

i cant wait for SP3

Hmm, that looks interesting. But in my tests, setup doesnt go ahead without a key (clean installs booted from CD). I can imagine this behaviour changing over time, but as of now its nothing except hassles for the layman (as its probably meant to be, so thats probably not an issue)!

As for SP2c, I dont see it solving any customer issues, since it has no new hotfixes. Its likely meant to tighten control over keys & activation procedures.
About SP3, its probably not so much about long & painful, as it is about 100% thorough testing for the last ServicePack of the largest selling OS..... And MS isn't likely to include ie7 or wmp11, or indeed any other new features, simply because a large proportion of users currently on XP dont want those updates (plus, offering those separately as feature-packs helps to motivate a few more people to go genuine). Also, since win2k, MS has pledged to keep ServicePacks plain & simple, with only patches, and any extra features would have to be obtained separately - and this has almost never been violated - some servicepacks since then do seem chock-full with new stuff but that is only a relative measure.

Either way I'm not very optimistic about the future of XP. Clean and simple are two very relative notions, for example to nLite users that means one thing and for Microsoft a totally different thing. Keeping the project line of XP Fundamentals for Legacy PCs just for OEMs is the proof.

I still remember the evolution of the NT 4.0 SP line, as I never used Win 95/98 on my computers. And I believe I am seeing the public impact of discontent caused by the aging product when it reached the milestone XP is now aiming towards. Sure, my customers need XP, but I wouldn't use it for myself. I did not use it when it was Gold back in 2001, and I wouldn't use it now. I've been using server products for 7 years now, and I am very happy with them. Even more now, as Server 2008 got Aero...

So, good luck for the poor guys at Microsoft trying to rollup a 5-year old codebase to today's requirements. They sure need it.

What do you think was done with Vista and Server 2008? Both of those are essentially rollups of a previous code base.

obviously.

Hi ive just slipstreamed pre sp3 to xp all worked untill installing the P-Key has been changed and not accepting my cor key.

i had to use the default key on disc but as you would probly know its an 30 day activation job.

i was reading a post from "ricktendo64" stating that he had to mod some files to accept the cor key.

can anyone give me an idea as to how this can be done?

matt121@optusnet.com.au

thanks.

its possible but not sure July Updated Direct X 9.0c

Nope, there are no directX updates, its the same old dX9c from early 2004.

matt121, no this is not supposed to be done, and any posts related to this can be considered warez.

I got some questions regarding this SP3 beta and the final SP3 (whenever that'll be...)
Once this "beta" or "final" version becomes "available" for the "public". Will it, or should I say... It seems that this beta release is already supported with the current Nlite release(s).
So what I'm wondering is... Would if be safe to slipstream SP3/SP3beta untop a SP2 slipstreamed Gold CD? Or..
Should I use my Gold CD to slipstream this beta or final version, and forget about SP2? Or should I just slipstream SP2 and then SP3?

I've read about that SP3 holds the current hotfixes dated back to SP2, so should it be safe to use RyanVM's Post-SP2 Update Pack (which will probably be renamed to SP3...) untop this SP3 beta or final release? I mean.. wont it interfere with the SP3 hotfixes that are already intergrated when slipstreamed?
This is of course common sense that it would, but since im not sure whatever Ryan's Post-SP2 Update Pack holds all hotfixes dated back prior (I assume it does) to SP2?

I'm also wondering if anyone knows if this goddamned SP3 will contain .NET Framework 2/3?

Edit: I assume that this will be the same case as it was with SP1 > SP2.

This post has been edited by Chrno: Aug 29 2007, 01:15 PM

Firstly, SP3 is unlikely to contain any version of dotnet framework or IE7 or WMP11, or any other *NEW* features. It is all going to be security & stability patches, that is all.

As for the slip-streaming, you should preferably do that on top of your Gold CD.
Why is that? because SP3 contains all updates released previously (including SP1, SP2, and everything from the post-SP2 updt pack). So using a non-Gold-CD as a starting-point, will result in a mess (a mess consisting of XP+SP2+SP3+useless CAB files + orphan leftover junk....)







In short, yes you can forget about SP2. But this beta may not be fully ready for the general public yet, what with its CD-key problems and all....

Hi could someone pls advise me where i can download win xp sp3 every link i have tried seem to be disbled

cheers

mcmuzzy

The beta for XP SP3 is still private, so legally you would have to be part of the private beta (usually being a beta Microsoft customer) or a Technet or MSDN customer, and you would then download it directly from MS. Please don't ask for links to download this, thank you.

YAY MSDN!!!

Yup, MSDN/Technet this month.

So when is the final build going to be released, any news on this?

Seriously, Microsoft should have released this a while ago. Too busy on Vista I guess.