I don't care what OS you're using you're always going to need some backward compatability. It's one of the things that distinquishes RedHat from other linux distros.
I still like to use some of the old desktop themes, because they are beautiful and give my desktop a unique appearance. Aesthetics are still important to me.

..and for those folks who need it, download is a great option. Including features or "themes" used by maybe 1% of your user-base is a waste.

I agree that there needs to be a clean split and really Vista was the time that should have been done. XP is certainly a stable enough platform and many will use it for years to come so no reason why that couldn't have been the last one with legacy code.
With the amount of time it took them to create Vista, they certainly had time to clean out legacy code and I'm sure they did some, but not enough.

Here's some help, dont use Vista until they fix all the flaws!

Clearly Microsoft's decision to move past an obsolete help file format is a "flaw" ...what an asshat you are.

While his comment could be considered trolling, the name calling isn't really necessary.

They may no longer use the hlp format in their programs, but it's clear that people still run programs that do use it since Microsoft has been getting complaints about it since Vista came out.

It's a flaw in decision making - to cut off users who still use old hlp formats and in the same breath tell them how great and technologically advanced Vista is. Yeah, technologically if you do it *our* way.

I think part of the issue is that Microsoft is trying to shed some of their legacy software and legacy support structure (which the .hlp format is), but they are discovering that the users are resisting those attempts. In this respect Microsoft is trapped between two cliffs... one where they are yelled at for supporting old computing technology, and one where they are yelled at for attempting to get rid of that same technology. By providing a way for users who want to hold on to the old structure is at least commendable, but if you're talking Vista then Microsoft needs to really go beyond that and seriously junk all of the Win9x legacy and make it clear WHY it needs to be junked.

It is not really a flaw. They need to start shedding the old legacy code from Windows. Just look at the jumbled mess that Vista's code has become (look how long it took and how big the code base is).

I think the next major version of Windows desperately needs to start removing some of the legacy functionality that is wasting space in Windows. By the time the next major version of Windows is released most users will be on Win Vista or Win XP (we're talking probably 2010 for the next major release of Windows). They should cut it off right there. If you're not on XP by the time they release the next version then you are left in the dark. I am ok with that. Microsoft can't keep supporting the people who refuse to upgrade/update it just hurts them during development.

A flaw in decision making? To cut a format that's been dead for years? Just to appease some lazy-ass document writers who can't migrate a freaking .hlp file?

Give me a break.

Started with DX9.

Damn near everyone here whined about it. Can you imagine if they went x64 and dropped x86 cold turkey?

They can't win. Cut the bloat by dropping support for older tech and piss off users of the older tech, or keep support and piss off users of the new tech for having a lot of "useless" bloat.

For context-sensitive (What's This?) help in applications, *.HLP files are still used, and was therefore 'broken' when running on Vista, that is, until Microsoft offered this patch.

THat's Linux screwed if you're going to apply that rule to an OS.

Not included because no-one uses it!=broken.

*Note: "no-one"=0+/-1%

"For context-sensitive (What's This?) help in applications, *.HLP files are still used, and was therefore 'broken' when running on Vista, that is, until Microsoft offered this patch."

Since Windows 98, Microsoft has standardized on the HtmlHelp (CHM) format, which is HTML based and provided all the features of WinHelp (HLP) and more. Nearly 9 years later they deprecated the WinHelp format. If developers cannot get up and fix their apps to be compliant with an easier to use format, then it is the developers - not Microsoft - that need to be corrected. It is about time the Microsoft dropped support for WinHelp.

For that matter, with Vista Microsoft started the deprecation process for their HtmlHelp format, but still provides support. (Vista uses something new, what? I don't know. But HtmlHelp was officially dropped as of Vista. Vista will still use and render it, however.)

Hmmm, Apple dropped PowerPC and switched to Intel , yet made it possible for users to continue running most PowerPC apps (including heavyweight stuff like Office, Photoshop, and even some real-time music stuff).

It CAN be done!

--->Can you imagine if they went x64 and dropped x86 cold turkey?

Sure. I never said it couldn't be done. Reading comprehension can be your friend.

As for Apple...

People whined and moaned and complained about the bloat and performance issues the "fat" binaries caused to no end.

...which was kinda my point. :)

They also had an amazing amount of 3rd party dev support.

This is not an update, but it's an optional component WinHlp32.exe (only avaible on Microsoft Download Center and not on Windows Update) for users want to see obsolete .hlp files.

Really...how hard would it have been for MS to include this in Vista and not have a problem? Noooooooooooo, they'd rather create a problem that doesn't exist while at the same time telling everyone about the 'WOW'.

Everyone...don't forget the 'WOW'.

Anyone?

Yeah. That'd be perfect.

Let's make darn sure tech no-one uses anymore is 100% supported outright by the OS. I mean, it's not like you asshats don't think Windows is already bloated or anything, right?

Let's support DOS and Win3.1 apps while we're at it. Sheesh...

ace move

Reading help files are like asking for directions. You don't do it until you've exhausted every other possible option.

Besides, that's what Google is for. :p

Micorosft?

Yeah, everyone knows it should be Micoros FT.

is probably a patent thing ....
you cant spell the company's name
otherwise they'd sue you ...