Jump to content

The count-down to SP2


prathapml

Which language (of Windows) do you use?  

219 members have voted

  1. 1. Which language (of Windows) do you use?

    • English
      154
    • German/Japanese
      7
    • Others
      42


Recommended Posts


According the experience of Microsoft Taiwan, they will release Windows XP SP2 Traditional Chinese Version next week.

Because they usually release the patches and updates of the Traditional Chinese version after Microsoft USA has released them since one day. (After 1 day of releasing, Microsoft Taiwan will release them.)

Link to comment
Share on other sites

OK, as you all know, SP2 has been RTM'ed and the build to get approval was finalised on Aug4 as originally planned. It wanted 2 days more of just-to-be-****-sure testing, and then got released on Windows Beta. So now, logically this thread comes to a close.

A final, small clarification to those of you who got the SP2 final from non-Official sources, and have a question needing to be resolved before it RTW's officially, so that you can be ahead of others in the race:

You know that the details of the final SP2 are as follows-

Filename: WindowsXP-KB835935-SP2-ENU.exe

Filesize: 266 MB (278,927,592 bytes)

Build: 2180 (RTM) from WindowsBeta

md5sum: 59a98f181fe383907e520a391d75b5a7

Name of Signer : Microsoft Corporation

Digital Signature: Wednesday, 04 August, 2004 11:06:58

CRC: 0x046F12B1

Now, there was one thing worrying/puzzling a lot of people over at places where the leak was being discussed - the obtained file's (got thru P2P networks) time-stamp in the digital signature wasn't matching the above, and nor was the MD5 checksum, although CRC and all else was fine.

The reason is, the time-stamp mentioned above is GMT - therefore, since I am in a different timeZone (IST, +05:30), the time-stamp says "Wednesday, 04 August, 2004 3:36:58 PM" for me in file-properties, and gives an MD5 of "8b44385f22db7f8a6121273df8545a89". Since windows uses the GMT-time encoding to give a different reading for the time-stamp, the MD5 sum changes when you try generating/comparing it as well. So, if you are in doubt about whether you got/downloaded the correct file, consider your time-zone and check if the Digital Signature is accordingly displayed - if so, you got a genuine file.

Hoping this helps...........

Link to comment
Share on other sites

Even when changing the timezone, the md5 remains the same.

Its a shame many people are getting the wrong service pack (the one that ends in RTM_ENU.exe) from some chinese site believing its the real thing when its not: 1. It has no digital signature. 2. Its rumoured to be a repack of build 2162. 3. the md5 differs from the one ending in 5b5a7.

Link to comment
Share on other sites

Its a shame many people are getting the wrong service pack (the one that ends in RTM_ENU.exe) from some chinese site believing its the real thing
true....

Especially, when it is such an important update, and the main reason they are getting it early is to have it early on corporate networks, to improve security/reliability - and all they are getting is a possibly virus-ridden download.

BTW, mentioning the CRC32 checksum result (CRC: 0x046F12B1) as well, in the sticky would be enormously helpful, because that is really the only factor which is common when you want to compare the copy you downloaded as to whether you've got a genuine SP2.

Link to comment
Share on other sites

Think I'll wait on the real McCoy cause no telling what's in those ahem un-official releases...

Got this in email a little bit ago

Windows XP Service Pack 2 (SP2) has been released to maunfacturing.

The relevant end-user schedules for 2004 are:

August 06 Release to manufacturing.

August 09 Release to Microsoft Download Center (network installation package).

August 09 Release to MSDN subscription site (CD ISO image).

August 16 Release to Automatic Updates.

August 16 Release to Software Update Services.

August xx Release to Windows Update.

Not much time to wait on real thing..

Link to comment
Share on other sites

BTW, mentioning the CRC32 checksum result (CRC: 0x046F12B1) as well, in the sticky would be enormously helpful, because that is really the only factor which is common when you want to compare the copy you downloaded as to whether you've got a genuine SP2.

Added, but md5sums are still better :)

Link to comment
Share on other sites

[big snip by nolookingca]

The reason is, the time-stamp mentioned above is GMT - therefore, since I am in a different timeZone (IST, +05:30), the time-stamp says "Wednesday, 04 August, 2004 3:36:58 PM" for me in file-properties, and gives an MD5 of "8b44385f22db7f8a6121273df8545a89". Since windows uses the GMT-time encoding to give a different reading for the time-stamp, the MD5 sum changes when you try generating/comparing it as well. So, if you are in doubt about whether you got/downloaded the correct file, consider your time-zone and check if the Digital Signature is accordingly displayed - if so, you got a genuine file.

Hoping this helps...........

I have EST here and everything checks out...*confused*

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...