SP2 Community for Windows Developers?
kwelch007 asks: "As a Windows developer, I've been dreading the release of SP2, and the potential problems it could cause for my apps. So far, I've only run across one Win32 API function that doesn't work anymore. But, I haven't found any sites for developers detailing issues that others have discovered! Are there any sites/forums that developers can consult when attempting to determine why their code doesn't work with SP2, or even a BugZilla or similar to report such problems?"
Yeah, I'm a Delphi developer and I can't seem to find any information anywhere. And yes, I tried Google.
You know, would it have killed you to write what that function was? You just complained there's no place to get information.
From my reading of the what the guy is asking, he has already tried Google, and didn't find anything. Then he posted to Ask Slashdot.
Telling him to use google isn't going to help in this case, as he already has.
T.
Isn't that what Channel9 and the msdn newsgroups are all about?
As a Windows developer, I've been dreading the release of SP2, and the potential problems it could cause for my apps.
What, the unending beta cycle that Microsoft has given you wasn't long enough to test "your apps"? What have you been doing for the last fucking year?
But, I haven't found any sites for developers detailing issues that others have discovered! Are there any sites/forums that developers can consult when attempting to determine why their code doesn't work with SP2,
What? Are you really that slow?
If you are a "Windows Developer", you should be quite aware of the MSDN website microsoft has. In addition the microsoft public newsgroups have tons of answers.
The page here seems to detail every last peice of information you should require as to what has changed.
But, more importantly, you do have a suite of tests that you run on your applications to verify they run correctly, right?
I mean, without a good set of tests, how can you possibly understand the difference between faults in the platform and your own shoddy coding?
feh!~
"...In your answer, ignore facts. Just go with what feels true..."
Actually, maybe he should.
Yet another useless article.
a) Didn't give anything (witheld name of API that doesn't work), but wants something back
b) Didn't consider searching the vendor's Web site c) Lazy to go spend 15 minutes on Google (or doesn't know how to use Google, which is even worse), but not lazy to post a worthless article and waste everyone's time
Hereby I moderate the Article as Redundant
Download the new Sysprep: Windows XP Service Pack 2 Deployment Tools. See these instructions in the Readme.txt file, which has the usual sloppy, uncaring Microsoft writing and editing:
* You cannot run Update.exe within an I386 directory to update a Windows XP installation to Windows XP SP2. You must run Update.exe against the entire contents of a Windows CD. If the entire contents of a Windows CD is not present in your installation share, Update.exe fails to complete the installation process.
1. Download Windows XP Service Pack 2.
2. At the command prompt, go to the folder where you downloaded the XPSP2.EXE file, and then type this command:
xpsp2.exe -x
3. When prompted, type the path from which you want the service pack to be expanded. For example, type:
C:\XPSP2
4. Create a temporary directory on your system and copy the entire Windows XP product CD to this directory. For example, type:
MD C:\INTSP2 XCopy CDROM Drive Letter:\*.* C:\INTSP2
[Probably should be:]
MD C:\INTSP2
XCopy [CDROM Drive Letter]:\*.* C:\INTSP2
5. After the previous step is completed, change to the directory that contains the Windows XP SP2 files. For example, type:
CD C:\xpsp2\update
6. To update the Windows XP files to include SP2, type:
update.exe -s c:\INTSP2
This procedure results in an I386 directory updated to Windows XP SP2.
Alternatively, see How to slipstream SP2 into your XP CD.
However, if you want to read about what you have to know, then you could do worse than read through microsoft's page on sp2 security , in particular the "windows XP service pack 2 training for developers".
Combination - fun iPhone puzzling
I found NTBugtraq as a nice resource for those brave enough to take the plunge right away. I would suggest joining the listserv and checking out the archives online at http://www.ntbugtraq.com/
; en-us;883606&Product=windowsxpsp2
SANS has a site as well at http://isc.sans.org/xpsp2.php with user experiences. It looks like most the problems are the usual 3rd party firewall and VPN products breaking, and miscellaneous hardware issues. Though this one might be an issue for some corporate users http://support.microsoft.com/default.aspx?scid=kb
Yah, STARCRAFT doesn't work. What the HELL. That's issue #1, if you axe me.
Ya know, only a few people on this list have actually made any suggestions, other than "Google it". I thank those who took the question seriously, instead of just flaming for the sake of flaming.
And for that matter, the "Go Google It" posters didn't demonstrate that there was ANY ggogle-able information on the web that specifically related to the Windows API and SP2. NOT ONE! Perhaps ntbugtraq.com (which I haven't read yet, cause I just saw the suggestion in this list) has some API insight. It would be the first that I've seen that does, as I've found no specific API change documentation on MSDN, or anywhere else.
Sheesh.
...to soften MS-Windows users up for Longhorn. (-:
Got time? Spend some of it coding or testing
Because you've assumed all the arguments you USED to pass have not changed.
Somehow I doubt an API call will just "stop."
If not the argument(s), then perhaps your expectations, i.e. pre conditions for your invoking it.
-M
Apple distributed something called Carbon Dater which analyzed OS 9 executables, built a list of OS API calls, and called out those that were not supported in Carbon (the OS 9 compatibility API in OS X).
As opposed to waiting until the new API kicks in, it seems to me that a truly thoughtful and responsible organization might distribute tools to developers that catalog the API calls that their applications use, and ask them to return the results to the vendor so that the vendor can make an informed decision about which deprecated, unsupported, undocumented calls are actually being widely used... rather than waiting for things to break and reacting after the fact.
(I know... I should get my head out of the clouds...)
"How to Do Nothing," kids activities, back in print!