Windows 2000 Unofficial SP5 SR1

[Schadenfroh]

Text

Microsoft Windows 2000 Unofficial SP5 combines 403 hotfixes into a single hotfix - fully automated. It's not just a matter of determining file versions, there's much more to it. The interface is very easy to use since it's identical to a normal Windows update setup.

Anyone try it yet?

 

[rmrf]

I don't think I would try an unofficial service pack, for any OS.

 

[Canterwood]

Might have a look on a test box.

 

[ValuedCustomer]

Originally posted by: rmrf
I don't think I would try an unofficial service pack, for any OS.

Especially from someone called "Gurgelmeyer". -- that said, I'll be interested to hear what Canterwood finds w/ his test-box.

 

[Dovermen]

There will be no Service Pack 5 for Windows 2000, but instead Update Rollups. This seems to be a simular topic, but official.

http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollup.asp

 

[stash]

Why would you even post this? Installing this would be beyond retarded.

 

[redbeard1]

I've had really good luck using the "Unofficial Service Pack for Windows 98". Of course I tested it on non production systems a few times.

Can this be any worse than MS kicking out updates that break systems? Like the one that slowed computers down that were using certain anti virus programs, or the one that causes problems with VPN tunnels because it doesn't allow fragmented MTU packets. Or when they kicked out the Win2k security roll up, and crashed a number of servers because of how the new printer file definitions were handled?

I had to get a Hotfix from MS for an issue with the event viewer files getting corrupt. It said it was for SP5. Now where does that fix go? Do you still have to call and beg MS to fix what they didn't get right the first time?

Who knows, this unofficial version may work better. Throw it on a test box or two and see.

 

[stash]

I had to get a Hotfix from MS for an issue with the event viewer files getting corrupt. It said it was for SP5. Now where does that fix go?

That's just a naming convention. All fixes post service pack x are named with x+1.

Can this be any worse than MS kicking out updates that break systems?

A MS update won't have a root kit in it (cue rabid slashbot freaks).

 

[MrChad]

Originally posted by: redbeard1
I've had really good luck using the "Unofficial Service Pack for Windows 98". Of course I tested it on non production systems a few times.

Can this be any worse than MS kicking out updates that break systems? Like the one that slowed computers down that were using certain anti virus programs, or the one that causes problems with VPN tunnels because it doesn't allow fragmented MTU packets. Or when they kicked out the Win2k security roll up, and crashed a number of servers because of how the new printer file definitions were handled?

I had to get a Hotfix from MS for an issue with the event viewer files getting corrupt. It said it was for SP5. Now where does that fix go? Do you still have to call and beg MS to fix what they didn't get right the first time?

Who knows, this unofficial version may work better. Throw it on a test box or two and see.

As with any software patch for any piece of software, you should install and test the patch in a QA or testing environment before rolling it out to production.

I believe all hotfixes are labeled with a service pack number after the current SP. All new XP hotfixes are labeled SP3 and all new 2000 hotfixes are labeled SP5.

 

[spyordie007]

Can this be any worse than MS kicking out updates that break systems?

A MS update won't have a root kit in it (cue rabid slashbot freaks).

Or how about the fact that MS patches are supported. If one of those hoses your system at least you can get support for it...

 

[hooflung]

Originally posted by: spyordie007

Can this be any worse than MS kicking out updates that break systems?

A MS update won't have a root kit in it (cue rabid slashbot freaks).

Or how about the fact that MS patches are supported. If one of those hoses your system at least you can get support for it...

Just like dell giving onsite next day support for their laptops if you purchase that warrenty? Sure thing pal, I would read the fine print first.

 

[stash]

Just like dell giving onsite next day support for their laptops if you purchase that warrenty? Sure thing pal, I would read the fine print first

Support for issues related to a patch is always free. Just call the number.

 

[mikecel79]

Originally posted by: hooflung

Originally posted by: spyordie007

Can this be any worse than MS kicking out updates that break systems?

A MS update won't have a root kit in it (cue rabid slashbot freaks).

Or how about the fact that MS patches are supported. If one of those hoses your system at least you can get support for it...

Just like dell giving onsite next day support for their laptops if you purchase that warrenty? Sure thing pal, I would read the fine print first.

I've gotten onsite next day support on Dell laptops before. As a matter of fact when one of our salesmen dropped the laptop and broke the screen they came the next day to replace it. Of course we had Complete Care coverage so it covers accidents like that. I've also called Microsoft about a patch that broke a system before and we never got charged a single cent. As a matter of fact there is a KB article on Microsoft's site because of the call. You can view it here if yoru really interested.

It sounds to me like your either trolling or you've never actually called them before.