Slashdot Mirror
Complete List of Bugs Fixed in SP2
callipygian-showsyst writes "Microsoft has published the complete list of bugs fixed in Service Pack 2.
They range from the obscure like: 'File Appears to Be Deleted Although You Do Not Have Permissions on the OS/2 Warp4-Based Server' to the serious-sounding: ' Stop error message on a blue screen when you transfer data to a USB device in Windows XP'"
It's not a dupe. The one you listed is SP2's incompatibilities. This is a list of things it fixes.
This list is all the bugs that have been fixed in Windows XP through SP2, not bug fixes exclusive to SP2.
To update the list of last accessed files? To save different recording preferences like bitrate, input device, etc?
Windows XP keeps a list of programs recently run in the registry I believe... hey you asked! :)
SP1 fixed very serious bugs in Win XP that were not on the SP1 bug list. Also, serious bugs that had been reported a long time before were NOT fixed.
How is the Windows icon derogaroty or belittling?
/.
If you look very closely, its either a very nice stained glass window, or each pane is cracked.
I leave the decision of which it is to the reader, who shoudl bear in mind that this is
Hmm, I'm reading it as PRB: You Cannot Use XML Serialization on a Class with Declarative Security but maybe they have a problem with their database and you see things differently.
This was probably submitted by a company that enforces pushed fixes. I'm just guessing but I've worked in places where bugs are submitted & fixed and you see some weird stuff that actually makes sense if you know the context.
Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\Advanced, make entry EnableBalloonTips, set REG_DWORD to 0
Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
The save dialouge also records where the last place saved to is.
What signature defines me as a person?
Outlook Express has no junk mail filtering.
If you recall, it used to have junk mail filtering. Then Blue Mountain Arts sued Microsoft and forced them to take it out - because not only were they not willing to work with MS to ensure that their greetings cards got through, but they were assinine bastards as well.
Coming soon - pyrogyra
Hey, assclown, don't plagiarize.
I can plagiarize and get an insightful moderation too. Watch:
"blah blah blah blah blah"
(+5, Insightful)
w00t!
http://www.microsoft.com/downloads/details.aspx?Fa milyId=049C9DBE-3B8E-4F30-8245-9E368D3CDB5A&displa ylang=en
A Service Pack provides an easy mechanism to identify major code refreshes. This way when handed two sets of install disks a person can tell if they have newer version than was originally distributed.
Now for the most part I agree, lots of this should be available for download separately. The update process in windows is tolerable. However there may be enough inter dependancies among these various updates to require them all to be available in one neat package.
I know people who will not use Windows Update but they will apply a service pack.
As for that 250Mb size, I believe that was the special network administrators version that everyone should not have been downloading, let alone the fact that most only got it because it was on P2P network.
* Winners compare their achievements to their goals, losers compare theirs to that of others.
So? Windows is fairly standard; there are many, many more possible Linux configurations, considering the range of platforms on which it runs, along with the vast number of distros. Then you have different compiler versions, glibc versions, kernel versions...
And yet bugfix updates always go smoothly, because the system was designed better in the first place. Small, standalone components working together -- that's what UNIX is all about. With Windows, however, it's a big shaky stack of old and new technologies hobbled onto one another, with ancient code that can't be removed because of design issues, and new code that has to be shoehorned in awkwardly.
Hey, I agree that it's tough for Microsoft. But it's not an excuse -- they should've designed and engineered the system much more cleanly and smoothly, so components could be bugfixed without others being affected. Many other OS vendors have managed this, even with still-running OSes that predate Windows, so you'd expect the world's largest and richest software company to have some kind of handle on it.
This the list of programs that the built-in firewall will break until you add them to the exception list. Be ready to do the procedure listed in the Knowledge Base article on every machine you apply the service pack to.
> If said program crashes, it could corrupt your registry, which is not a good thing.
The registry is transactional for that very reason (hey gconf, you listening?) and it's kept in HKEY_CURRENT_USER, so it won't render your system unbootable. Might make your profile very unhappy tho.
The reason it uses the registry and not a file is so it's kept in the profile. Mind you, the privacy implications of MRU's (ok, I'm thinking pr0n) make me wish it was in the Profiles\Application Data folder instead, then I could grep and delete at will. NTFS is a nice filesystem -- why doesn't windows try using it once in a while?
Related:
MS03-008: Flaw in Windows Script Engine may allow code to run.
And I thought it was supposed to do that...
The Windows Update process for installing the service pack does eactly what you describe. It scans the computer for what it needs to DL and it DLs only what the computer nees. It can range from about 70 to 90 meg Not the 250 to 400 meg for the full admin or developer versions.
/. users were supposed to be smart enough to figure things out for themselves by reading and experimenting rather than blathering on and on about things that they know nothing about to hords of other people that also know nothing thus starting up a shit storm of FUD like the wold has never seen"
In the same vein... "I thought that
Laptops.. they throttle the processor to increase battery life..
That's like saying you know where every configuration file is because it's stored somewhere under '/'.
(Although you do have a point about every program using a different syntax. Using the same syntax does really help all that much because you still have to understand the semantics of what you're changing to screw something up).
HAND.
as far as I know there is no tool bundled with Windows to allow you to edit the registry from the command line
...and the big easy:Insert your OS cd and (when prompted) "press any key". Select the "Repair Installation" option from the second screen to rebuild the registry and system files-- comparable to running an upgrade of Windows from the same version of Windows. It's the most complete solution for repairing your windows installation.
In Windows XP and the Windows Server 2003 products "reg.exe" is provided for command line registry manipulations.
Ex: reg query HKLM\Software\Microsoft\
To repair the registry:
- Boot to safemode (bang on f8 post-post and before the windows flag pops up, the menu options are there. This loads a minimal system, usually bypassing any badness you've perpetrated and allowing you to prune and update to your hearts content. You can even use System Restore to reteat to a prior (known good) configuration.
- Boot to the recovery console (minor recovery support -- mostly enable/disable services, really).
-
Sorry, but you're talking out your arse.
I installed SP2 and then it made me re-activate both Windows and Office 2003.
We've deployed it on approximately 100 machines here in the office, and haven't had any activation issues of any kind, with Visual Studio, Office, or Windows XP itself. I also fail to see how a service pack would force a re-activation.
spoke to numerous tech support and activation department employees before they gave me a new product key which could be re-activated. I felt like I was getting interrogated as to why I was re-activating the software
You've apparently never actually had to re-activate windows or office. The very first thing you can do is use the internet to re-activate. 90% of the time this works right off the bat. The second thing you can do is call their 1-800 number, and be connected to an automated phone system. You say/speak the code into your phone, and the system reads back an auth code. Bam, done. If for some reason the phone system cannot understand you, it transfers you to a Real Live Person (tm) who asks for your code, and gives you back an auth code. No interrogation. No questions at all, even.
Not All Who Wander Are Lost
The processor can't detect "empty clock ticks"... there's no such thing.
If the operating system determines that no user threads have anything to do, and the kernel has run out of stuff to do to... so it's just waiting for hardware interrupts (keyboard, mouse, network, video, disk, interval timer), rather than sitting around in a loop it executes the HALT instruction which brings the CPU into a low-power state until an interrupt or trap wakes it up.
Otherwise it would have to spin in a loop for a few milliseconds, and that eats juice it shouldn't otherwise need to.
Intel Speed Step CPUs let the operating system use special MTRRs that allow it to dynamically adjust the clock speed in reaction to an increase or decrease of thumb-twiddling time as well. Because a CPU at 1.2GHz halting 50% is still consuming more power than the same CPU at 800MHz in HALT only 20% of the time.
I believe this is the thing that doesn't work in XP without Service Pack II or hotfixes. I've heard about this gripe before.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON