New XP SP2 build

There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).

Dick wrote:
There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).

Whats the deal with installing that version (and indeed the release version)
over a slipstreamed RC2? I know you couldn't do it for a slipstreamed RC1
to RC2.

Want to upgrade to a slipstreamed XP SP2 at some point, but will wait for
the release version if I can't install over the top.

Cheers,

Ben
--
A7N8X FAQ: www.ben.pope.name/a7n8x_faq.html
Questions by email will likely be ignored, please use the newsgroups.
I'm not just a number. To many, I'm known as a String...

In article , , Dick
says...

There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).


Amazing how much effort they put in to Anti-Piracy & SP2. The windows
update page does recognize blacklisted serials (will not allow updates),
yet a keychanger & keygen has already been hacked to change serial to
get the updates. BIG waste of effort on their part...............

By all means wait for the SP2 release. I have a system that is dedicated
to testing SP2 betas so if there are problems I lose nothing but time.

Ben Pope wrote:
Dick wrote:

There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).


Whats the deal with installing that version (and indeed the release version)
over a slipstreamed RC2? I know you couldn't do it for a slipstreamed RC1
to RC2.

Want to upgrade to a slipstreamed XP SP2 at some point, but will wait for
the release version if I can't install over the top.

Cheers,

Ben

I don't think that it's windows update that recognizes blacklisted
product keys, I think it's just SP1 (and soon, SP2).

In one sense, your observation is correct, since Keygens exist, any
scheme based on a blacklist can be defeated.

However, in a different sense, your post is incorrect, because there is
a difference between "can be defeated" and the conclusion that it's
therefore useless. While it "can be defeated", it can only be (or
perhaps I should say "will only be") defeated by a relatively small
portion of the customer base, certainly no more than a single digit
percentage. From that perspective, the effort, although by no means
"watertight", is still very worthwhile in terms of Microsoft's efforts
to significantly decrease the number of customers using bootlegged
product keys.


ByTor wrote:
In article , , Dick
says...


There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).



Amazing how much effort they put in to Anti-Piracy & SP2. The windows
update page does recognize blacklisted serials (will not allow updates),
yet a keychanger & keygen has already been hacked to change serial to
get the updates. BIG waste of effort on their part...............

"ByTor" wrote in message
...
In article , , Dick
says...

There is a new build of XP released to testers, 2162. The last release
was 2149. That was RC2 (release candidate 2). Now MS has released build
2162 to its beta testers in a last ditch effort to make sure SP2 will be
ready for its August 'Prime Time' release.
I had no problems installing this build. If the final is like this build
we will not have any trouble with updates (assuming your PID is correct).


Amazing how much effort they put in to Anti-Piracy & SP2. The windows
update page does recognize blacklisted serials (will not allow updates),
yet a keychanger & keygen has already been hacked to change serial to
get the updates. BIG waste of effort on their part...............


Nah, it just keeps the honest people honest. Like locks on your doors.

Also beware of this build as it is an interim build, not meant for the
masses. Some folks have had real problems - then some folks always have
problems!

Steve
OldManCompute

"Steve Colburn" writes:
Nah, it just keeps the honest people honest. Like locks on your doors.

How many "honest" people do you know that go around testing locked
doors? Locks on doors keep stupid thieves out, that's all.

--
Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
Ronald Cole Phone: (760) 499-9142
President, CEO Fax: (760) 499-9152
My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B