Windows XP SP2, Build 2138 on Windows Update v5

SpinnerSpinner Birmingham, UK
edited July 2004 in Science & Tech
Today build 2138 of Service Pack 2 for Windows XP has appeared on Windows Update v5 as a recommended update. You can also download it manually at the link below. Just remember Windows Update v5 and SP2 are not yet finished, keep that in mind before you update.

Note: Corp users use caution!

Download (270MB)

Source: [url=][/url]

Comments

  • TexTex Dallas/Ft. Worth
    edited June 2004
    Why should the Corp users be any more cautious then usal Spinner? Mind sharing your reasonaing?

    Tex
  • shwaipshwaip bluffin' with my muffin Icrontian
    edited June 2004
    He's probably referring to the leaked xp pro corp users with the cd key fckgw-...

    MS may have put in some sort of check...don't wanna have the MS gestapo busting down your door.
  • TexTex Dallas/Ft. Worth
    edited June 2004
    For gods sake anyone still using that after all the covergae in the last few years deserves to be whacked.

    I've seen lots of crap posted of people having probs installing onto a sp1 system. Saw just as many posts on the forums around the net about SP2 RC1 blocking the corp copies and I'm on my 4'th sp2 versions and no probs yet including running windows update. But I always slipstream it onto a bare original version of XP so maybe thats the key I don't know.

    I'll slipstream this one and install tomorrow and let ya know.

    Tex
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Tex wrote:
    Why should the Corp users be any more cautious then usal Spinner? Mind sharing your reasonaing?

    Tex
    Certainly...

    Back when SP1 came about, a few known bogus product keys were blacklisted (e.g fckgw-) and at the time there was talk that Bill and the boys were going to blacklist any keys that were created using popular key generators such as the 'Blue List Keygen'. I think that's what it was called. That never happened as it turned out.

    Apparently genuine Corp product keys have a PID of 640 (e.g XXXXX-640-XXXXXXX-XXXXX). Most bogus product keys have a PID of between 641 and 649. I believe now, at least in this build of SP2, (I haven't tried previous builds) Microsoft have finally got round to blacklisting those bogus PID's, hence why I quietly tried to warn any naughty people round here that installing this build of SP2 on a pirated version of XP Corp (i.e using a non-Microsoft distributed product key) will render them unable to access their OS, because after the installation of the Service Pack, upon reboot, it will deny you access to Windows unless you activate the product. Which of course, you won't be able to do because it's using a bogus product key.

    See?

    So in a nutshell, this time, more than a few widely used bogus product keys have been blacklisted. Almost all of them have been rendered useless by method of higher levels of product authentication built into SP2, or at least this build.

    That's my reasoning.

    Cheers
  • MissilemanMissileman Orlando, Florida Icrontian
    edited June 2004
    I was gonna say I would give it a try and tell you if it did kill key generator numbers, but I just checked all mine and they show 640 so I guess it would work then.

    Now I do have 2 legal copies of XP Pro OEM, but my play/test machines use the corp version since I'm always redoing em and don't want to activate it 3 times a week :)

    This is really the truth too :) It is,,,, Really,,,,,,Really it is !!!!!!
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Missileman wrote:
    I was gonna say I would give it a try and tell you if it did kill key generator numbers...
    I've already tested it mate, it does kill all but the newest of key generator numbers. Like I said above. Which is great, because piracy is bad. :p

    ...and it doesn't matter what people use it for, if it's an illegal copy, it's illegal to use it.
  • MissilemanMissileman Orlando, Florida Icrontian
    edited June 2004
    Yes Sir - You are right. It killed the -640 PID on installation and reboot. So I started fuzzing it. A -642 key went right in and now says activated. Really weird. Need to explore this more.

    I do like a challenge.
  • Outcast-JediOutcast-Jedi Singapore
    edited June 2004
    My PID is like this "XXXXX-648-XXXXXXX-XXXXX". Does any of u have PID -648 and does it work without activation for the latest built?
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Outcast Jedi wrote:
    My PID is like this "XXXXX-648-XXXXXXX-XXXXX". Does any of u have PID -648 and does it work without activation for the latest built?
    I've tested a version with that PID yes, and it doesn't work. You have an illegal copy of Windows XP. Shame on you.

    There are obviously going to be 640 PID's which are blacklisted as well, just like they did with SP1, and there are going to be 641-649 PID's which will work, however like I said, 99% of 641-649 PID's will not work. At least that's what the tests I did, aswell as obvious reports accross the net indicated.

    The bottom line is, a new key with a PID of 640 is required for these illegal corp versions to continue working under SP2, at least for the most part.

    This is why it always pays to buy. Saves on the hassle. I cherish my OEM version of XP Pro with all my heart. £100 well spent.

    This whole situation is really quite ironic actually, considering only a month or so ago, there were reports that Microsoft were going to let SP2 allow it self to be installed on any copy of XP, pirated or not. So once again, whichever Microsoft exec' leaked that little piece of fiction out, they look all the more stupid now.

    Cheers.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited June 2004
    Didn't read the whole thread but AFAIK MS is not gonna do anything about the illegal versions.
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Anarchy wrote:
    Didn't read the whole thread but AFAIK MS is not gonna do anything about the illegal versions.
    Perhaps you should read the whole thread. :thumbsup:
  • TexTex Dallas/Ft. Worth
    edited June 2004
    Spinner I have had 4 differant builds of SP2 all rumored to block the keys and none have SO FAR in my testing... But I have not had time to install this build either. So thats why its hard to bust the chops of the MS exec saying tehy wouldn't block it also. In fact this is still beta so the final release may STILL not block it. But if you were Bill Baby wouldn't it be fun to make everyone runningv illegal keys crap in their britch's today anyway. Hell he probably just invested 100,000,000 bucks in a line of dry cleaners just to launder everyones soild underwear knowing Gates.

    My hunch is if they block it. That a new round of keygens will surface. And in the meantime you will see a bunch of "patch sets" with a few DLL's in them that replace the MS versions with ones that don't block or at least don't check the keys.

    Its a game of cat and mouse that will never end. If they quit building Corp versions then there would be patch sets from the hackers to get around activation again. All MS can ever hope is to make it difficult for the normal user but they won't beat the real hacker guys.

    Tex
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Tex wrote:
    Spinner I have had 4 differant builds of SP2 all rumored to block the keys and none have SO FAR in my testing... But I have not had time to install this build either. So thats why its hard to bust the chops of the MS exec saying tehy wouldn't block it also. In fact this is still beta so the final release may STILL not block it. But if you were Bill Baby wouldn't it be fun to make everyone runningv illegal keys crap in their britch's today anyway. Hell he probably just invested 100,000,000 bucks in a line of dry cleaners just to launder everyones soild underwear knowing Gates.

    My hunch is if they block it. That a new round of keygens will surface. And in the meantime you will see a bunch of "patch sets" with a few DLL's in them that replace the MS versions with ones that don't block or at least don't check the keys.

    Its a game of cat and mouse that will never end. If they quit building Corp versions then there would be patch sets from the hackers to get around activation again. All MS can ever hope is to make it difficult for the normal user but they won't beat the real hacker guys.

    Tex
    Well yea, that's very true. I wasn't insinuating that this is that much of a big deal in the grand scale of things. Most folk, will probably just find it a minor in-convenience. I'm just reporting what I know. Warning the naughty people that at least this build of SP2 can be expected to cause them un-necessary hassle. Not that I'm supporting those people who choose to use pirated software.

    Anyways, I think we've given the infamous corp reliant users enough information for now. I do suggest however Tex you do have a mess with this build. I'm also in the process of looking at build 2142, to see what that's like with regard to authentication. I don't imagine however it is any different to 2138. It will be interesting to see though what RC2 is like with regard to all this when that appears.

    Cheers
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Related news: http://www.short-media.com/forum/showthread.php?t=14927
  • TheBaronTheBaron Austin, TX
    edited June 2004
    that download of SP2 doesn't work. it keeps telling me that atapi.sys is in use by one of my programs. WELL DUH IT IS!!! how do i get this working, cause its not on windowsupdatev5
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    TheBaron wrote:
    that download of SP2 doesn't work. it keeps telling me that atapi.sys is in use by one of my programs. WELL DUH IT IS!!! how do i get this working, cause its not on windowsupdatev5
    You don't have to be using WU v5 for it to work, as Microsoft just gives you the above link anyways.

    I can't begin to fathom why it doesn't work. Are you saying you can't download it, or you can download it, but it doesn't install?
  • TexTex Dallas/Ft. Worth
    edited June 2004
    TheBaron wrote:
    that download of SP2 doesn't work. it keeps telling me that atapi.sys is in use by one of my programs. WELL DUH IT IS!!! how do i get this working, cause its not on windowsupdatev5

    It could be a bug in a beta version (grin) but I have had some probs installing almost every version of sp2 I have tried when I try to install just sp2. Every single one had worked GREAT when you slipstream it onto a XP install cd so that you install WITH sp2 included. It added support natively for a lot of devices and the installs go much smoother. It takes 30 minutes to do a repair install of XP with SP2 included this way but its worth it.

    Tex
  • 3DCS3DCS
    edited July 2004
    TheBaron wrote:
    that download of SP2 doesn't work. it keeps telling me that atapi.sys is in use by one of my programs. WELL DUH IT IS!!! how do i get this working, cause its not on windowsupdatev5

    I went thru hell looking for a solution for this when I needed to install SP1...
    the problem is if you have daemon tools installed or have installed it,
    just delete atapi.sys from your [windows]\system32\drivers directory

    ^_~
Sign In or Register to comment.