This is the Platform SDK for Windows XP Service Pack 2 Release Candidate 1. Developers can use this to build and test pre-release applications for Windows XP Service pack 2.
Microsoft Windows XP Service Pack 2 Platform SDK RC1
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Its a service pack. how many beta testing and releasing candidates does this thing need to work properly. is this supposed to be xp reloaded or whatever. if you are going to put out longhorn a few years later why dont these guys just work on that and stop posting screenshots and leak daily builds. hyping it like the second coming of jesus and slowly dropping features as time comes up has been happening for quite sometime.
As a Windows developer I am quite annoyed by these silly marketing gimmicks
This is the Platform SDK for the service pack not the service pack itself. AFAIK-This is the first public release of a platform SDK for the service pack.
OMG I thought a service pack was supposed to be for bug and security fixes??? What does anyone need a _SDK_ for a patchset?? Someone planning to write applications for bugs fixes?? Okay, I’m confused.
Well, if they introduce some features (like improved firewall), some new flags to existing APIs, you need an SDK.
Get it, run windiff on include subdirectories and see what have changed. It’s that easy.
”
Get it, run windiff on include subdirectories and see what have changed. It’s that easy.”
not at all that easy. you need complete api reference documentation with examples from msdn to understand all this. claiming otherwise is just plain wrong
easywrite/mount rainier is it supported?
not at all that easy. you need complete api reference documentation with examples from msdn to understand all this. claiming otherwise is just plain wrong
Yeah you need a COMPLETE NEW api to understand what has changed in XP SP2. Sure thing buddy.
All you need to be aware of is what changes SP2 makes that might effect your application. Thats it. Just like its always been with a service pack.
“Yeah you need a COMPLETE NEW api to understand what has changed in XP SP2. Sure thing buddy”
thats not what i said. i said windiff wont help and you need documentation for whatever said changed including api changes. thats obsolutely correct.
“All you need to be aware of is what changes SP2 makes that might effect your application. Thats it. Just like its always been with a service pack.”
no. MS is trying to sell a service pack as a stop gap measure before it releases longhorn. thats why they released “xp reloaded” and such stuff.
do you have any idea HOW LONG MS has been testing this stuff?
what about the kernel architecture goofups that made my system unbootable earlier?.
thats not what i said. i said windiff wont help and you need documentation for whatever said changed including api changes. thats obsolutely correct.
Right.. I’m with you.. and I’m also with the guy who posted about using windiff to see whats changed. Thats also correct. Whats the point of this ? To argue about how software developers deal with service packs ? ???
no. MS is trying to sell a service pack as a stop gap measure before it releases longhorn. thats why they released “xp reloaded” and such stuff.
What in the hell does that have to do with anything ? As a developer I need to be AWARE of what has changed in SP2 that effect MY software.
It has nothing to do with MS’s marketing position.
do you have any idea HOW LONG MS has been testing this stuff?
Nope. I’m not on staff nor the beta team.
what about the kernel architecture goofups that made my system unbootable earlier?.
You are all over the map here. In fact you’ve lost me with your ramblings… poor poor deranged soul.
The Platform SDK – Windows XP Service Pack 2 Release Candidate contains the information you need to develop applications for Microsoft Windows XP Service Pack 2 Release Candidate 1.
Use this SDK to ensure that you have the latest documentation, samples, and SDK build environment (header files, libraries, and tools) for the RC1 release of Windows XP Service Pack 2.
OMG I thought a service pack was supposed to be for bug and security fixes??? What does anyone need a _SDK_ for a patchset?? Someone planning to write applications for bugs fixes?? Okay, I’m confused.
Long sigh. In case you’ve lived under a rock for the past year: Microsoft wants SP2 to be good. SP2 is going to be a hell of a lot more than just a pile of previously released patches.
Well, even though I’m on the SP2 beta team (meaning I have access to SP2), I won’t be able to test it… Runnin’ Server 2003 as my Windows version of choice
”
Long sigh. In case you’ve lived under a rock for the past year: Microsoft wants SP2 to be good. SP2 is going to be a hell of a lot more than just a pile of previously released patches. ”
its just that
“Right.. I’m with you.. and I’m also with the guy who posted about using windiff to see whats changed. Thats also correct. Whats the point of this ? To argue about how software developers deal with service packs ? ??? ”
windiff wont help. so thats what is the argument
“poor poor deranged soul”
come up with better arguments
I’ve been working in the IT department for a new company for the last 5 months. We are currently reviewing beta versions of SP2, and we will likely deploy the new patch. Problem is that we have 1200+ workstations running WinXP, and we do NOT have Microsoft SMS — and we lost the budget for purchasing a copy.
I came from a company of 62 workstations. We used Microsoft SUS for critical updates, and when a new SP came out I simply went desk to desk to install the SP.
Question: Does anyone know of way to install Service Packs on WinXP to a LARGE community without using Microsoft SMS or running to each machine?
Any help or suggestions would be greatly appreciated…
Thanks, sorry for being a bit off topic!
Microsoft regularly releases updated versions of its Platform SDK (about 6-12 months apart) and gives the SDK the name of the product release that is closest to when it will be released. However, the Platform SDK does not target just that specific product release, since it’s really just a continually updated set of headers, libraries, documenation, and samples.
For instance, I regularly submit minor corrections/typos to the Platform SDK documentation and they just get incorporated into the next release. Sometimes they add new samples to clarify particular APIs, or new hyperlinks between related topics. And of course there are new APIs that get created/exposed (as with the release of Windows 2003 server, or Win XP SP2).
Prefacing this w/ “I am not an admin”
…
i believe you can use group policy via active directory (i am assuming w/ that many machines your LAN is on a domain), however i am not sure if that uses a push or a pull model for deployment. it’s pretty easy to set up and is very well documented on the web.