Windows XP SP2 Release..
Wednesday, August 4, 2004 by Frogboy | Discussion: WinCustomize News
It's about to go gold and be released to the public this month.
Microsoft will finalize the code for Windows XP Service Pack 2 (SP2) sometime today, release it via Microsoft Download Center and MSDN on the Web tomorrow, and then ship it to customers via Windows Update beginning August 25, though Automatic Update users will get it immediately on a staggered basis.
For those users running software that patches their system DLLs or hacks their kernal, expect a wild ride. In most cases new versions of those various patches will have to be applied.
And For those of you using say WindowBlinds or DesktopX or IconPackager (i.e. Object Desktop programs) SP2 should work fine with no updates required.
We'll keep you up to date on what problems we hear in various customization programs so that you're prepared.
 |
|
Page 2 of 2 | |
|
|---|
UBoB
Reply #22 Saturday, August 7, 2004 4:22 PM
Reply #22 Saturday, August 7, 2004 4:22 PM
According to a recent update on Paul Thurott's site: http://www.winsupersite.com/reviews/windowssp2.asp
"On August 6, 2004, Microsoft released Windows XP SP2 to manufacturing. You will be able to download this update starting the week August 9, 2004..."
"On August 6, 2004, Microsoft released Windows XP SP2 to manufacturing. You will be able to download this update starting the week August 9, 2004..."
PixelCargo
Reply #23 Monday, August 9, 2004 8:02 AM
Reply #23 Monday, August 9, 2004 8:02 AM
Link doenst work.
Sorry, the page you're trying to reach is temporarily unavailable or the page may no longer exist
I think his site gets alot of visitors
Sorry, the page you're trying to reach is temporarily unavailable or the page may no longer exist
I think his site gets alot of visitors
Enzyme
Reply #24 Monday, August 9, 2004 4:16 PM
Reply #24 Monday, August 9, 2004 4:16 PM
It's out: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/winxpsp2.mspx
The WindowsUpdate "Express" installation is apparently going to be available shortly, but the network install (large download for updating PCs without internet connection, multiple computers, etc) is available.
Phil
The WindowsUpdate "Express" installation is apparently going to be available shortly, but the network install (large download for updating PCs without internet connection, multiple computers, etc) is available.
Phil
[email protected]
Reply #25 Monday, August 9, 2004 5:49 PM
Reply #25 Monday, August 9, 2004 5:49 PM
I'm aware of only 3 potential issues with SP2, now that its gone RTM and
we've spent the day with it.
1. Sometimes BootSkin fails to load on the first reboot after installing the
SP. Reboot again and it should be fine.
These next two, as far as I've been able to reproduce, are specific to AMD64
based platforms.
2. WindowBlinds on AMD64's (builds prior to the WB 4.38 ones on SDC now).
The new NX memory features enabled by SP2 are a bit too sensitive. It'll prevent
skinning from working properly and cause display properties to crash while you're
opening it.
Apart from running the latest beta (4.4 official release will be out in
August, 2004), you can change your boot.ini parm from /NoExecute=OptIn to /Execute. Which disables that new feature, but works around the issue for the moment.
I will probably rebuild 4.3 to account for this as well, but its confined to
AMD64's.
If anyone is having trouble with WB on SP2 elsewhere, I need details.
3. CursorXP on the AMD64's is totally hosed on loading. The /Execute change
to boot.ini above deals with it on the one machine I've had a chance to test
with.
Symptoms on the machine here include a dialog about DrWatson crashing coming
up and everything locking. Hard reset necessary.
If you are experiencing problems with CursorXP on non-AMD64 platforms,
again, I need details. Does it crash at the end of the install? Does it crash while
loading the images? What's the crash information?
Use SmartException (http://storage.stardock.com/files/smartexception.exe) to
capture additional debug information to \program files\common
files\stardock\smartexception\cursorxp.exe.cra) and send support or myself that.
we've spent the day with it.
1. Sometimes BootSkin fails to load on the first reboot after installing the
SP. Reboot again and it should be fine.
These next two, as far as I've been able to reproduce, are specific to AMD64
based platforms.
2. WindowBlinds on AMD64's (builds prior to the WB 4.38 ones on SDC now).
The new NX memory features enabled by SP2 are a bit too sensitive. It'll prevent
skinning from working properly and cause display properties to crash while you're
opening it.
Apart from running the latest beta (4.4 official release will be out in
August, 2004), you can change your boot.ini parm from /NoExecute=OptIn to /Execute. Which disables that new feature, but works around the issue for the moment.
I will probably rebuild 4.3 to account for this as well, but its confined to
AMD64's.
If anyone is having trouble with WB on SP2 elsewhere, I need details.
3. CursorXP on the AMD64's is totally hosed on loading. The /Execute change
to boot.ini above deals with it on the one machine I've had a chance to test
with.
Symptoms on the machine here include a dialog about DrWatson crashing coming
up and everything locking. Hard reset necessary.
If you are experiencing problems with CursorXP on non-AMD64 platforms,
again, I need details. Does it crash at the end of the install? Does it crash while
loading the images? What's the crash information?
Use SmartException (http://storage.stardock.com/files/smartexception.exe) to
capture additional debug information to \program files\common
files\stardock\smartexception\cursorxp.exe.cra) and send support or myself that.
PixelCargo
Reply #26 Tuesday, August 10, 2004 9:33 AM
Reply #26 Tuesday, August 10, 2004 9:33 AM
Slipstreaming Sp2 on Paul's site
http://www.winsupersite.com/showcase/windowssp2_slipstream.asp
http://www.winsupersite.com/showcase/windowssp2_slipstream.asp
PixelCargo
Reply #27 Wednesday, August 11, 2004 10:10 AM
Reply #27 Wednesday, August 11, 2004 10:10 AM
Hmm that method didnt work for me, just do a search on google and go to the link thats iamnotageek.com or something like that, its simpler and worked for me.
uspsfedex
Reply #28 Monday, August 16, 2004 11:55 PM
Reply #28 Monday, August 16, 2004 11:55 PM
Wow, I'm having the same problem as "Nakor"
Using CursorXP for awhile now, with no probs, then I updated to SP2, now, I can't load CursorXP w/o Explorer constantly restarting, finally hardlocking.
I'm also using an AMD Athlon 64, motherboard: MSI K8N Neo Platinum.
This problem also occurs on a fresh install of a slipstreamed WinXP SP2.
Glad to see I'm not the only one with this problem.
Hope that helps.
Using CursorXP for awhile now, with no probs, then I updated to SP2, now, I can't load CursorXP w/o Explorer constantly restarting, finally hardlocking.
I'm also using an AMD Athlon 64, motherboard: MSI K8N Neo Platinum.
This problem also occurs on a fresh install of a slipstreamed WinXP SP2.
Glad to see I'm not the only one with this problem.
Hope that helps.
agsebastian
Reply #29 Friday, August 20, 2004 5:25 PM
Reply #29 Friday, August 20, 2004 5:25 PM
Hi guys,
Is it safe to admit that I've been beta testing weekly builds since the inception of XP SP2? Well over a year an a half. Don't slamm me, please. I did it so I could put my best input into the release.
Everybody interested in doing this, if they honestly tested WinXP SP2 w/o slamming Microsoft or the OS, we'd end up with a way better release of the OS. MS depends on its beta testers to put the final product together, and they listen to us. Some of us found some problems with the original RTM released last weekand. MS tested our defect reports, found them valid, and were responsive enough to actually delay the release and fix the problems. So, don't think being a volunteer tester is a waste of time. This time around, MS really went the extra mile to listen to us on a number of issues that were mostly minor, but might mess up an easy install. Some others were more specific to program compatibility. And a few were serious enough to warrant code rewrites because of potential problems that may occur, not immediate ones.
But, hey, I haven't seen anyone rain on ATI's parade because the majority of us w/9800XT's or 9800 Pro 256 units can't get Doom 3 to run on our machines. Even with a gig of memory and 2.5 gig processors.
And I haven't heard much about Carmak and ID Software getting trashed for releasing Doom 3 without doing adequate QA on all platforms.
I spent full price on Doom 3, and all it does is decorate my shelf and hog up disk space. Crasheds about every three or four minutes. That is shameful and totally disrespectful. It is the tactics of the "old" Microsoft.
I've got the latest "Final" running on my machine right now without any problems. No issues with bootskins or logon skins, or w/Window Blinds or Object Desktop. I'm running the "Official" release of the Spiderman WB pack - which I think Stardock should remove the ISP text from on the wallpaper. Why should I have to pay for an advertisement for some ISP I don't care about? PLEASE redo the skin w/the spiderman-isp junk removed from the wallpaper.
To be really sure you're not going to corrupt anything, uninstall and then einstall al the Object Desktop apps and other specialty apps.
I keep every mod made to my desktop in a folder w/subfolders for every suite, keeping all wallpapers. logons, bootskins, etc. in the appropriate subdir. That makes it way easier to deal with.
Other friends have said that all they did was revert back to the Win XP default, and after the the installation, the switched back to Object Desktop and had no problems.
Feel free to post any questions about SP2. I'll do all I can to help you prepare for a good install. And I'd prefer not to get flamed or trashed, OK? I'm just trying to help, and ask a few questions about other buggy software that nobody trashes the way they do Microsoft.
Is it safe to admit that I've been beta testing weekly builds since the inception of XP SP2? Well over a year an a half. Don't slamm me, please. I did it so I could put my best input into the release.
Everybody interested in doing this, if they honestly tested WinXP SP2 w/o slamming Microsoft or the OS, we'd end up with a way better release of the OS. MS depends on its beta testers to put the final product together, and they listen to us. Some of us found some problems with the original RTM released last weekand. MS tested our defect reports, found them valid, and were responsive enough to actually delay the release and fix the problems. So, don't think being a volunteer tester is a waste of time. This time around, MS really went the extra mile to listen to us on a number of issues that were mostly minor, but might mess up an easy install. Some others were more specific to program compatibility. And a few were serious enough to warrant code rewrites because of potential problems that may occur, not immediate ones.
But, hey, I haven't seen anyone rain on ATI's parade because the majority of us w/9800XT's or 9800 Pro 256 units can't get Doom 3 to run on our machines. Even with a gig of memory and 2.5 gig processors.
And I haven't heard much about Carmak and ID Software getting trashed for releasing Doom 3 without doing adequate QA on all platforms.
I spent full price on Doom 3, and all it does is decorate my shelf and hog up disk space. Crasheds about every three or four minutes. That is shameful and totally disrespectful. It is the tactics of the "old" Microsoft.
I've got the latest "Final" running on my machine right now without any problems. No issues with bootskins or logon skins, or w/Window Blinds or Object Desktop. I'm running the "Official" release of the Spiderman WB pack - which I think Stardock should remove the ISP text from on the wallpaper. Why should I have to pay for an advertisement for some ISP I don't care about? PLEASE redo the skin w/the spiderman-isp junk removed from the wallpaper.
To be really sure you're not going to corrupt anything, uninstall and then einstall al the Object Desktop apps and other specialty apps.
I keep every mod made to my desktop in a folder w/subfolders for every suite, keeping all wallpapers. logons, bootskins, etc. in the appropriate subdir. That makes it way easier to deal with.
Other friends have said that all they did was revert back to the Win XP default, and after the the installation, the switched back to Object Desktop and had no problems.
Feel free to post any questions about SP2. I'll do all I can to help you prepare for a good install. And I'd prefer not to get flamed or trashed, OK? I'm just trying to help, and ask a few questions about other buggy software that nobody trashes the way they do Microsoft.
PixelCargo
Reply #30 Tuesday, September 14, 2004 9:49 PM
Reply #30 Tuesday, September 14, 2004 9:49 PM
Same here
SP2
AMD Athlon 64, motherboard: MSI K8N Neo Platinum.
\
Windowblinds installs but does not skin, only changes basic colors.
Getting blue screen and reboots due to driver pool conflicts.
SP2
AMD Athlon 64, motherboard: MSI K8N Neo Platinum.
\
Windowblinds installs but does not skin, only changes basic colors.
Getting blue screen and reboots due to driver pool conflicts.
the Red Death
Reply #31 Saturday, October 9, 2004 7:16 PM
Reply #31 Saturday, October 9, 2004 7:16 PM
I just downloaded the SP2, was running all the starduct trial stuff. Boot screen, WindowBlinds, Object Bar, icons, cursors, SymMetrics, Beatnik,and maybe a couple more. I have AMD Athlon 2600, TI4200 G-Force FX 128mb Graphic Card. Have a DVD-r/CDRW Burner, and a LG 52x CD Burner. Iomega Zip Drive from 1998 internal 100mb, a floppy drive from 1998 and had raid 0 and 1 gig of PC 2700 ram. Won't restart. My sister inlaws did the same thing, had to reformat hers. Why is microsoft releasing this if it is so unstable. I know 2 out of 3 people that have downloaded it and only 1 of them had a sucessful install. Do you see anything in my sysspecs that could be the problem "Agsebastian"?
the Red Death
Reply #32 Saturday, October 9, 2004 7:18 PM
Reply #32 Saturday, October 9, 2004 7:18 PM
P.S. I have a Soyo I have a SOYO dragon mother board and a 450 watt power suppy, 2 7200rpm 40gb Maxtor harddrives for the raid. WHAT SHOULD I DO?
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 2 of 2 | |
|
|---|
Reply #21 Friday, August 6, 2004 7:05 AM
New stuff new bugs. Some bugs are very specific like Lan printers wont work etc, weird small stuff like that.