Windows SP3
- Thread starter Punk
- Start date
One idea would be to manually create a system restore point just prior to seeing SP3 installed. If you should run into any problems you can use that to bring the system back.
The other option is uninstalling the new service pack by the add/remove and having the "show all updates" option checked off. The service pack should however go on without problem and contains some 1,000+ fixes MS finally got around to releasing for XP there.
The other option is uninstalling the new service pack by the add/remove and having the "show all updates" option checked off. The service pack should however go on without problem and contains some 1,000+ fixes MS finally got around to releasing for XP there.
Thanks for you ranswer.
Those are good ideas, I appreciate the help
Any news about AMD compatibility?
The Windows update site will see an AMD patch for dual and quad core model cpus. Which model/socket type are you running there?
The main support page for AMD is seen at http://www.amd.com/us-en/SupportDrivers/ProcessorSupport/0,,15218_15219,00.html
For the Sempron line the driver/utility page is seen at http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_11686,00.html
The main support page for AMD is seen at http://www.amd.com/us-en/SupportDrivers/ProcessorSupport/0,,15218_15219,00.html
For the Sempron line the driver/utility page is seen at http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_11686,00.html
That AMD compatibility thing with SP3 was only with OEM computers. There was a Intel file that was loaded by the OEMs that when SP3 was installed, when booting would freak out with a AMD processor. Most OEMs already have a patch for it. But if your building your own, nothing to worry about. I,ve probably loaded SP3 on 50 AMD machines.
You shouldn't see any problems with SP3 going on with just a quick glance at the specifications. The last build here saw a 939 board with 2gb of memory but the faster Atholon 3500+ 2.2ghz model. Note that with a slower cpu it will simply take a little more time seeing the large service pack go on fully.
Once on and working well Windows will seem to run better from what I've been hearing. I currently have that on for XP while seeing Vista as the primary OS at this time also seeing SP1 on for the new version. Having a much faster system now that didn't seem to make any difference as far as the update is concerned.
Once on and working well Windows will seem to run better from what I've been hearing. I currently have that on for XP while seeing Vista as the primary OS at this time also seeing SP1 on for the new version. Having a much faster system now that didn't seem to make any difference as far as the update is concerned.
Any time you install any large service pack or other large change in Windows there's always a change something will goo haywire. The link there simply shows a possible problem and rememedy due to how that model is configured not simply from having an AMD cpu.
Since HP is providing a patch of their own downloading it and saving it to a folder for safe keeping would be a recommendation in the event you run into the problem outlined there.
Since HP is providing a patch of their own downloading it and saving it to a folder for safe keeping would be a recommendation in the event you run into the problem outlined there.
As far as the Vista theme for XP I generally avoided them all together after an initial look on the last build here. The fixes and other things seen with the latest service pack may be causing a new version problem for that.
On some systems the first install of SP2 saw a number of issues until a second attempt saw that actually go on well. The overall condition of Windows or a simple bad install may be the reason why there was a problem.
A second attempt may see SP3 go on without a hitch. Look at the startup items and disable anything not essential to rule out a software clash from an antivirus, firewall, or some other program getting in the way. It's always a good idea to manually create a restore point before seeing any large update go on anyways in case of a problem.
On some systems the first install of SP2 saw a number of issues until a second attempt saw that actually go on well. The overall condition of Windows or a simple bad install may be the reason why there was a problem.
A second attempt may see SP3 go on without a hitch. Look at the startup items and disable anything not essential to rule out a software clash from an antivirus, firewall, or some other program getting in the way. It's always a good idea to manually create a restore point before seeing any large update go on anyways in case of a problem.