Slashdot Mirror


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?"

38 comments

  1. That's exactly what I'm looking for... by Yuioup · · Score: 3, Funny

    Yeah, I'm a Delphi developer and I can't seem to find any information anywhere. And yes, I tried Google.

    1. Re:That's exactly what I'm looking for... by kwelch007 · · Score: 3, Insightful

      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" people didn't demonstrate that there was ANY information on the web that specifically related to the Windows API and SP2. NOT ONE! Perhaps ntbugtraq (which I haven't read yet, cause I just saw the suggestion in this list) has some API insight. Its the first that I've seen that does, as I've found no specific API change documentation on MSDN, or anywhere else.

      Sheesh.

    2. Re:That's exactly what I'm looking for... by Anonymous Coward · · Score: 0

      Ya know, only a few people on this list have actually made any suggestions, other than "Google it".

      Slashdot has a mailing list?

  2. one API function? by Anonymous Coward · · Score: 5, Insightful
    I've only run across one Win32 API function that doesn't work anymore

    You know, would it have killed you to write what that function was? You just complained there's no place to get information.

    1. Re:one API function? by MarsDefenseMinister · · Score: 3, Funny

      He might be talking about the InfectSystem () function, which is heavily used by viruses. I wonder if he checked the LoadSpyware () function to see if that worked.

      --
      No weapon in the arsenals of the world is so formidable as the will and moral courage of free men.-Ronald Reagan
    2. Re:one API function? by kwelch007 · · Score: 5, Informative

      LOL. Actually, it was CreateToolbarEx(), which is documented on MSDN as obsolete, so I wasn't sure it was worth mentioning specifically.

    3. Re:one API function? by scupper · · Score: 2, Informative

      Here's another one I spotted, or rather "googled", http://www.winprog.org/ then started snooping around. Post back here when if you do/don't find what you're looking for from the suggestions.

    4. Re:one API function? by kwelch007 · · Score: 1

      Works fine on every Windows patch previous to XP SP2...never saw any documentation that pointed this fact out. Do you think that no other developer has software out that uses MSDN documented "obsolete" funtionality? Rediculous.

      I wrote the question becuase I am sure that other similar inconsistencies/undocumented changes exist, but are not well known to the developer community.

  3. Re:Answer: google.com by Tomahawk · · Score: 3, Interesting

    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.

  4. msdn.general and channel9 by scupper · · Score: 4, Informative

    Isn't that what Channel9 and the msdn newsgroups are all about?

    1. Re:msdn.general and channel9 by scupper · · Score: 1, Informative

      might also drop in on http://blogs.msdn.com/

    2. Re:msdn.general and channel9 by ribond · · Score: 0

      I'm an enabler... Along with Channel 9, here's the official MS collection of xpsp2 technical resources:

      http://support.microsoft.com/default.aspx?scid=fh; ln;windowsxpsp2it ...and here is the stuff they have for developers (security-feature oriented, mostly)

      http://msdn.microsoft.com/security/productinfo/XPS P2/default.aspx ...and here is one of the MS hosted communities where you can read/post/enjoy xpsp2 dialog.

      http://communities.microsoft.com/newsgroups/defaul t.asp?icp=xpsp2&s

  5. Huh? by His+name+cannot+be+s · · Score: 5, Insightful

    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..."
    1. Re:Huh? by Anonymous Coward · · Score: 0
      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?

      Sorry, but you're running off into assumption land during your rant. It started off good though.

    2. Re:Huh? by Anonymous Coward · · Score: 0

      Assumptions? He said he is "dreading what will happen" Sounds like he hasn't run any tests. My development team has had a group investigating SP2 for the last 2 months.

    3. Re:Huh? by Anonymous Coward · · Score: 0

      Answer: Asking my boss for permission to install SP2 so that I can test, and being denied because it's beta. We are NOW allowed to test it, and supposidly, the end users can NOT install it till we clear it. Welcome to "the real world"

    4. Re:Huh? by Anonymous Coward · · Score: 0

      Taken from your blog:

      "I'm a software developer by day. I earn what most would be a very fine living. I am completely immersed in technology. Last count, over 25 programming languages, and 26 different Operating systems and platforms. I own 10 or so computers in my house. I have cat 5 cabling to every single room, excluding bathrooms, 44 runs in all. I've got a wireless router, a PocketPC phone, complete with 1x wireless networking and sdio support for my wifi. I have a satellite dish."

      Not everyone's an expert like you are. Instead of ripping the guy a new ass, just give him some advice and let it be. There's no need to be such a dick about it.

    5. Re:Huh? by His+name+cannot+be+s · · Score: 1

      True, but where else can you be a dick and still get modded up to 5?

      My Point, (posted before the doctor adjusted my litium dose) is that Microsoft specifically left a rather large margin of time for the gentleman to test Service Pack 2. With apparently little concern for the inevitable, he chose not to test before it went "Gold" -- a misnomer to be sure.

      If he (and by extension, the company he works for) is unwilling or unable to test SP2 prerelease, maybe software development is not for him.

      So, to those I offended with my snarky attitude, I am sorry. But, then again, I am also tired of the I'll wait attitude of others. Fair Exchange. :P

      --
      "...In your answer, ignore facts. Just go with what feels true..."
  6. Re:Answer: google.com by madaxe42 · · Score: 5, Informative
  7. Article Mod: Redundant by Donny+Smith · · Score: 1, Flamebait

    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

    1. Re:Article Mod: Redundant by Anonymous Coward · · Score: 0

      The worst part is that this got posted to slashdot at all. The editors couldn't be bothered to do the simple analysis that you just did.

  8. MS Official: Slipstream SP2 into Windows XP. by Futurepower(R) · · Score: 2, Informative


    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 /e

    [Probably should be:]

    MD C:\INTSP2

    XCopy [CDROM Drive Letter]:\*.* C:\INTSP2 /e

    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.

  9. Guide to changes by Chris_Jefferson · · Score: 1
    Unfortunatly, XP SP 2 involves major changes, and a simple short list isn't going to help (in terms of altering existing applications, I would say XP SP 2 is the biggest change ever, as usually microsoft is very careful to not break previous code, up to maintaining old bugs).

    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
  10. Try out NTBugtraq by phenix927 · · Score: 1

    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/

    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; en-us;883606&Product=windowsxpsp2

  11. From the... by boarder8925 · · Score: 0, Offtopic
    from the strenght-in-numbers dept.
    I believe that should be strength. ;)
  12. Re:Answer: google.com by Anonymous Coward · · Score: 0

    Mod up the original poster! The /.'er who wrote to ask /. obviously didn't google... or try hard enough! Slacker!

  13. Re:Answer: google.com by Anonymous Coward · · Score: 0

    Maybe the "asker" should have gone to "Ask Google instead of "Ask Slashdot"

  14. Starcraft by bobo+the+hobo · · Score: 2, Funny

    Yah, STARCRAFT doesn't work. What the HELL. That's issue #1, if you axe me.

    1. Re:Starcraft by Anonymous Coward · · Score: 0

      Yah, STARCRAFT doesn't work. What the HELL. That's issue #1, if you axe me.

      Well, if I take a fucking axe to your skull, I don't think you'll be too worried about Starcraft. Ergo, it's not issue #1.

  15. Sheesh by kwelch007 · · Score: 1

    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.

    1. Re:Sheesh by Anonymous Coward · · Score: 0

      Ya know, only a few people on this list have actually made any suggestions, other than "Google it".

      Which list are you subscribed to? Is this a mailing list? Are you really that fucking stupid that you don't know the difference between a mailing list and a fucking website? Did your parents have any children that lived?

  16. A sample from the MSDN Security Dev Center by Anonymous Coward · · Score: 0
    Spotted this in my wanderings through ribond's enabling my journey in msdnland. The title gave me pause for though. :X Fine-Tune Your Web Site for Windows XP Service Pack 2

    Fine-Tune Your Web Site for Windows XP Service Pack 2

    Microsoft Corporation
    July 2004 Applies to: Microsoft Active X controls Microsoft Internet Explorer Microsoft Outlook Express Microsoft Windows XP Service Pack 2 (SP2)

    Summary: Make your Web site work well with the new security features in Windows XP SP2 that affect ActiveX controls, file downloads, pop-up windows, and more. (7 printed pages)

    Topics include: Does Your Web Site Use Microsoft ActiveX Controls?
    Does Your Web Site Allow Users to Download Files?
    Does Your Web Site Use Pop-up Windows?
    Does Your Web Site Depend on the Microsoft Java Virtual Machine (MSJVM)?
    Browser Window Restrictions
    General Tips Does Your Web Site Use Microsoft ActiveX Controls? In Windows XP Service Pack 2 (SP2), the modal installation prompt for ActiveX controls will be initially suppressed using the Information Bar. An exception is made for upgrades to controls that have already been installed on the computer, providing that they meet the following criteria:
    • The file registered as the ActiveX control must be signed with Authenticode technology. (This file is referenced from HKEY_CLASSES_ROOT\CLSID\{control_clsid}\InProcServ er32, where control_clsid is the CLSID specified by the OBJECT tag.)
    • The publisher name in the digital signature of the new control matches the publisher name in the digital signature of the existing control.
    • If the ActiveX control is packaged in a CAB file, the CAB file must be signed. The DLL or OCX to be installed should also be signed in order for subsequent upgrades to bypass the Information Bar.

    If the Information Bar suppresses an ActiveX control and the control takes up area on the page, Internet Explorer will show an inline icon and text in place of the control indicating the ActiveX control needs to be installed. End users will be able to click on this area or the Information Bar to install the ActiveX control.

    Is the ActiveX control distributed in a cabinet (CAB) file? If so, be aware future installation prompts to upgrade this control will also be suppressed by the Information Bar unless you sign the DLL or OCX to be registered as the ActiveX control. Does your Web site have different behavior based on whether an ActiveX control was installed (for example, automatic redirect or special behavior on refresh)? Some Web pages automatically redirect or behave differently when refreshed after a control is not installed. In some cases, building your site this way might prevent the user from being able to install the control, providing a bad user experience.

    Since a Web page cannot distinguish between the user declining the installation of an ActiveX control and the control getting suppressed by the Information bar, the recommended practice for installing an ActiveX control is to create an instance of the control on a standalone Web page that explains the purpose of the control. Also, use a section within the tag to dynamically show Help text to the user for installation failures. Does your Web site have images of the Authenticode dialog? In order to prevent user confusion, you can update these images to reflect the new Authenticode user interface (UI). You can use the user agent string to determine the correct version of the browser. (See General Tips for more information on detecting SP2). Does the ActiveX Install
  17. I personally suspect that SP2's a covert action... by leonbrooks · · Score: 1

    ...to soften MS-Windows users up for Longhorn. (-:

    --
    Got time? Spend some of it coding or testing
  18. CodeProject.com by Anonymous Coward · · Score: 0

    http://www.codeproject.com

    This is the definitive community for MS developers. There will be SOMEONE there to help you.

  19. Maybe it doesn't work.... by betelgeuse68 · · Score: 1

    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

  20. Why not "API coverage analyzers?" by dpbsmith · · Score: 1

    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...)