pendanticist

msg:567850 | 5:33 am on Aug 10, 2004 (gmt 0) |
I'm curios. If it's been released, why does it not appear at Updates page as available? I've heard...'this week'. Pendanticist.
|
tedster

msg:567851 | 5:43 am on Aug 10, 2004 (gmt 0) |
| Aimed at IT professionals and administrators, the full network install package weighs in at a lofty 270 MB, and is thus unsuitable for most average users. However, if you're waiting for the Automatic Updates or Windows Updates release of XP SP2--and all indications are that you likely will continue to wait for some time--and have a broadband account, the full network installation package might be just a ticket. Windows .NET Magazine [winnetmag.com] |
|
|
operafan

msg:567852 | 5:56 am on Aug 10, 2004 (gmt 0) |
MIght not be relevant to this post but How do I actually save those patches onto a CD & install it on other PC's with the same OS? I've heard it on TechTv but I don't know how to go about it. ANyone? Thanks
|
Hester

msg:567853 | 9:07 am on Aug 10, 2004 (gmt 0) |
I heard it was just 80Mb and you could use Auto-update to get it in chunks.
|
brat

msg:567854 | 11:54 am on Aug 10, 2004 (gmt 0) |
Oddly enough, IBM has said that no one in their company can install SP2 due to issues. Story is covered on ZDNet and Slashdot. "...IBM last week told employees to hold off installing SP2 until Big Blue can fully test and customize it. The company's technology department said the delay is "due to known application problems and incompatibility with IBM workstation applications."
|
encyclo

msg:567855 | 12:03 pm on Aug 10, 2004 (gmt 0) |
Welcome to WebmasterWorld, brat. The IBM story is in fact almost entirely spurious. I know someone who works for IBM, and with over 500,000 Windows machines on their internal network, IBM uses their own Windows Update mechanism including their own customized patches. The warning was simply standard practice and a reminder that IBMers should be using the company's update process not going out on their own. The possible incompatibility issues are due to the customization of the IBM Windows installation against which MS would not have tested. It is the same situation for every medium to large business which manages their Windows updates centrally.
|
bulldog

msg:567856 | 1:19 pm on Aug 10, 2004 (gmt 0) |
I've been using the pre-release version for a couple of weeks, no problems at all. I plan on rolling it out to all my internal clients when the public release has been issued.
|
MatthewHSE

msg:567857 | 2:01 pm on Aug 11, 2004 (gmt 0) |
| Maybe I'm being subliminally encouraged to upgrade? |
| Maybe . . . why don't you try upgrading your browser to FireFox and see if IE stops crashing? ;)
|
Lord Majestic

msg:567858 | 2:05 pm on Aug 11, 2004 (gmt 0) |
| Oddly enough, IBM has said that no one in their company can install SP2 due to issues |
| Its typical of big companies - it is not uncommon for them to threaten abandon support of their own software on client boxes if client anyhow modifies it without authorasation. Of course this is also a lucrative revenue stream resulting from authorised changes.... But to be fair I am with IBM on this one - people don't really know what they are upgrading, and fundamentally living few more weeks on as unprotected boxes as last few (2?) years makes sense in order to avoid business disruption. With all sneaky changes like limiting number of open connections to any given port I am not suprised they want to thread carefully - personally I prefer to learn on others experience first :)
|
Chndru

msg:567859 | 2:07 pm on Aug 11, 2004 (gmt 0) |
Is there anything on this SP2, that would make me go "I have to install this?" [added] [support.microsoft.com...] [edited by: Chndru at 2:40 pm (utc) on Aug. 11, 2004]
|
flashfan

msg:567860 | 2:24 pm on Aug 11, 2004 (gmt 0) |
F Y I | 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. Microsoft considers Windows XP Service Pack 2 as an essential security update and is distributing it as a 'critical update' via Windows Update (WU) and the Automatic Updates (AU) delivery mechanism in Windows. Microsoft is strongly urging customers with Windows XP and Windows XP Service Pack 1-based systems to upgrade to Windows XP Service Pack 2 as soon as possible. |
|
|
Conard

msg:567861 | 12:27 am on Aug 12, 2004 (gmt 0) |
I just ran the IT update on this machine and it was the least painful experience I have had with a major Windows update so far. Not to happy with how the pop up blocker will block any java script pop up even if a link is clicked. Looks like a few hundred pages to update on my main site.
|
Purple Martin

msg:567862 | 12:42 am on Aug 12, 2004 (gmt 0) |
| why don't you try upgrading your browser to FireFox and see if IE stops crashing? ;) |
| hehe, Firefox is my normal-use browser, but of course I have to test in IE. | Not to happy with how the pop up blocker will block any java script pop up even if a link is clicked. |
| Wow, is that the new IE standard behaviour? This means unscrupulous webmasters will stop bothering to write popup code! Hooray!
|
tedster

msg:567863 | 12:59 am on Aug 12, 2004 (gmt 0) |
That was NOT in the early descriptions Microsoft released - in fact, just the opposite. Opt-in (clicked-on) pop-ups were explicitly allowed, and that's the only sane choice I can see for a pop-up blocker. In XHTML 1 strict, using the target attribute for a new window is not allowed, so this makes ANY new window either invalid or impossible. Not a good thing at all.
|
Conard

msg:567864 | 2:23 am on Aug 12, 2004 (gmt 0) |
The default setting on the pop up blocker is medium. If you set it to high it will break all java script pop ups and I use them for "More Information" in product ordering. It will also break all target="_blank" links set at high. I think that feature may stop the average person from setting it there.
|
Compworld

msg:567865 | 2:56 am on Aug 12, 2004 (gmt 0) |
Yea, I have to say, the SP2 upgrade was painless. The SP2 works great. You may just have a corrupt file in your Windows directory. CompWorld
|
tedster

msg:567866 | 5:01 am on Aug 12, 2004 (gmt 0) |
| The default setting on the pop up blocker is medium. If you set it to high it will break all java script pop ups... |
| Good - that is as promised.
|
MatthewHSE

msg:567867 | 12:02 pm on Aug 12, 2004 (gmt 0) |
| hehe, Firefox is my normal-use browser, but of course I have to test in IE. |
| Sigh, yes that's my case too. The unfortunate realities of life . . . ;) So besides the popup blocker, what else is new in XP SP2? I'm on W2K, with no opportunity (or frankly, desire) to "upgrade" to XP. Still, I like to keep informed. Anything else of interest to web developers?
|
Hester

msg:567868 | 9:21 am on Aug 13, 2004 (gmt 0) |
This page lists known problems found so far, along with a list of features SP2 installs: [news.bbc.co.uk...] | Some of those responding mentioned that it took a couple of hours to install the update which, for business firms, weighs in at 266MB. The version for home users is likely to vary in size depending on whether users have kept up to date with past updates to XP. |
|
|
|