|
Anton Afanasyev wrote: Vista can really be thought of as a "new OS".
I agree somewhat, but I think 95/98 to NT/2000 was a bigger delta for a "new OS".
With the 95->NT, or XP->Vista conversion, the opportunity to start anew and correct the driver DLL hell were laid at their feet, to correct mistakes originally made. So far, it's still broke.
Anton Afanasyev wrote: They don't become "outdated".
I disagree here. If the peripherals don't work anymore, then they are outdated for that O.S. Sure, the hardware still works if you have the old OS running somewhere, but for the purposes of the discussion, the peripherals are now worthless - they don't work. They need updated. Now, if the manufacturer creates a driver for the new O.S. the updated driver will un-outdate the peripheral.
Anton Afanasyev wrote: In reality, there are absolutely NO problems writing drivers for every single piece of hardware that ...WinXP supports in order to make them compatible with Vista.
Well, this is the gist of my problem. Every manufacturer should not have to write a driver for a new version of an OS. The new OS comes out, the old driver should work fine. Maybe not with any whiz-bang capabilities the new OS might offer, but they should work. Think of the cancel button on the GUI. I can run my old app in Vista, but it has the fixed-size X button unless I rewrite the app because there was no way to size it differently from the others. (Yeah, I know there's a "way", but that's not the point here.)
If MS came out and said, "we're sorry, but Vista requires a redesign of drivers, but you'll never have to do it again" that would be a much better story to tell than "we're sorry, but Vista requires a rewrite of the drivers just like last time and next time."
But, that's just my opinion. 
Gary
|
|
|
|
|
ghle wrote: Designing changes into Operating Systems changes (versions, upgrades, revisions, call-it-what-you-like) that are not compatible with existing driver methodology is the problem.
But hardware manufacturers are also to blame here. There was an old driver model, and many drivers didn't follow the rules, but somehow just worked. A new driver model comes, with backward compatibility for good old drivers, and those bad old drivers cease to work. Whose fault is it?
MS goes to great lengths to support old software in newer versions of Windows. Maybe that is why Windows is so bloated; it has just too many compatibility hacks. Have you ever read Raymond Chen's blog[^]? He sometimes explains compatibility hacks, and the great length MS goes to ensure an old program that doesn't follow rules still works.
|
|
|
|
|
|
Its time for codeproject community to be the third party 
|
|
|
|
|
Given the amount of suckage in the usual HP software (think supermassive black hole at the center of our galaxy), why would you want it anyway?
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Given the amount of suckage in the usual HP software (think supermassive black hole at the center of our galaxy), why would you want it anyway?
So we could add enough stuff to eventually fill up the black hole? 
Gary
|
|
|
|
|
I'm seriously disillusioned with pissed at HP at the moment.
I've owned several HP printers, all of which have been fantastic from a hardware perspective. They're reliable, last practically forever, and aren't too painful on consumables. Their driver software has always been crap, but the Windows builtin support worked well.
That was true until my most recent purchase. I bought an HP PhotoSmart CS5240. It's a scanner/printer combination.
The software was the usual HP nightmare. At the end of the installation, it had two HP Photosmart printers in the my device list. The first one was disabled and offline. The second was enabled, but only for photo tray printing. After an hour of cussing, multiple reboots, and strong words with the Device Manager, I got that mess straightened out. I could finally print.
Good Lord, what a piece of noisy junk! This thing sounds like it's a Borg with epilepsy. Printing a page requires 30 seconds of clanking before it even gets paper into the printer. Print quality is OK, but not awe-inspiring. The thing sucks ink like an alcoholic. My daughter's printed a little over a dozen 4"x6" photographs, and the color cartridge is empty. I figure the thing costs around $1.50 per photograph, which is ridiculous.
At the moment I don't think I will ever buy another HP product. I'm stuck with this one, since I can't get a refund based solely on "poor performance".
Software Zen: delete this;
|
|
|
|
|
You would get along very well with Rajesh. Maybe you can form a club.
Cheers,
Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically.
Harris' addendum: I think you meant "monotonously".
Martin's second addendum: Jeffersonian... I think that should at least get a mention.
|
|
|
|
|
If they drop driver support, they should at least make the driver source code available so we can develop drivers on our own for new OS's.
As far as support, if the device is still in production (or still in the retail channel) when the "new" version of Windows comes out, they should have drivers for it.
Lastly, avoid buying the multi-function printers. You're always going to be faced with driver problems regarding one or more functions of the printer.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Until the time that they clearly mention when selling the product. However no one bothers identifying it in advanced. What prevents any company to say that I'll support you for 5 years, for example?
// "In the end it's a little boy expressing himself." Yanni
while (I_am_alive)
{
cout<<"I love to do more than just programming.";
}
|
|
|
|
|
Hamed has hit the nail on the head. Make a commitment and stick to it. That's what my company does. We invested a huge amount of effort in updating drivers for Vista for products we don't even sell any more. With a clear commitment, customers can decide for themselves.
And this business of asking a bunch of enterprise programmers to make a marketing decision for peripherals manufacturers? Downright silly. Of course they're all going to say "a damned long time" because anybody who hasn't written a mass-market driver for a non-trivial device thinks it's easy.
|
|
|
|
|
Sure it's not easy and I don't defend the thesis of supporting it forever but at least 2 generations!
We see hardware coming out not compatible with Vista, only XP and this is not acceptable but if the hardware was bought to Windows ME  I don't demand it to be supported on Vista.
Another problem I know it happens is that companies don't want the drivers to last too long because they want to sell the hardware. Not supporting old hardware on new OS's is the easiest way to "force" a customer to upgrade its piece.
|
|
|
|
|
You mean my HP550C might not work under Visa?
But it ran under 3.1, 95, 98SE, and XP Pro, and is only 15 years old!
Shame on you HP!
Bob Emmett
|
|
|
|
|
Bob Emmett wrote: You mean my HP550C might not work under Visa?
Not one of those H-1B Visas, anyhow. http://en.wikipedia.org/wiki/H-1B_visa[^]
Seriously, I did expect a 2-month old HP digital camera to work with the new HP Vista computer. After tech instructions to reload the camera OS, new (free under warrantee) USB cables, reload the OS, untold hours on phone with tech support, they finally owned up that the camera, even in USB external drive mode, was not compatible with Vista. That's inexcusable.
Gary
|
|
|
|
|
Maybe so, but it's an entirely different issue.
|
|
|
|
|
integer-poet wrote: Maybe so, but it's an entirely different issue.
What is? I don't follow. 
Gary
|
|
|
|
|
Vista was out over a year ago. You bought a camera two months ago. Vista pre-dated the camera. The manufacturer either claimed, before sale, that it was compatible with Vista, or it didn't. Either you noticed, before sale, or you didn't. If you had bought the camera two years ago and today the manufacturer still had not released Vista-compatible software, you'd have an on-topic complaint. As it stands, you don't.
|
|
|
|
|
integer-poet wrote: If you had ... you'd have an on-topic complaint. As it stands, you don't
Sorry poet, you misunderstood my post. By "new" computer, I didn't mean it was purchased yesterday.
The HP camera was purchased Christmas of 2006. The HP computer with Vista was purchased new in February of 2007 - 2 months later. I don't know if Vista predated the camera, but it's development sure did. The HP web site already had Vista software for the camera.
So, on topic, the OS and HP should have supported a camera that was 2 months old. The camera cannot even be considered legacy, outdated, or obsolete even today, 12 months later.
Both camera and computer were purchased from main-stream retailers, not some fire-sale web site. The camera worked fine with both XP and Win2K, just not the Vista machine.
Brings up another question - one we were left with: which is broken, the camera with it's Vista-specific software, or the computer with the Vista operating system? Which does the user return, the camera or the computer? HP blamed Microsoft, not the HP hardware or software.
Windows - the gift that keeps on giving.
Gary
|
|
|
|
|
Either the camera claimed to be compatible with Vista or it didn't.
Either Vista claimed to be compatible with the camera or it didn't.
Either you noticed or you didn't.
There is no such thing as "should" when it comes to technological compatibility.
|
|
|
|
|
integer-poet wrote: There is no such thing as "should" when it comes to technological compatibility.
Sure there is. When the camera claims to be compatible but it's not, normal people, and even people like me and the HP techs, say "it should be."
For a refresher, the survey you're responding to is: How long should a company continue to develop drivers for old hardware on new Operating Systems?
This wasn't even old hardware!
Gary
|
|
|
|
|
When the manufacturer makes an explicit claim, then there's no need to ask how long a device "should" be supported. The manufacturer already explicitly told you. There's no need for debate with a contract in place. Were I you, I'd demand my money back.
And yes, I know what the survey question says. As I've said, I think it's a deeply silly question because, among other reasons, it uses the word "should." But of course I'm assuming it's intended to be a constructive question, when that is really beside the point at best. The real purpose of the question is to make eyeballs stick on the site. And it's obviously working on me and you.
|
|
|
|
|
If it's coming out now incompatible with Vista, and that's not clear before purchase, then you have a legitimate complaint, but it's an entirely different complaint from the one behind this survey.
If you bought it two years ago and it's not compatible with Vista now, with no hope in sight, then at least you're on topic, but my claim is that you're in no position to tell a manufacturer, even as one of their customers, what its marketing policies ought to be. Either the manufacturer made you a promise of forward compatibility or it didn't, and either it kept that promise or it didn't. There is nothing else.
And no, manufacturers do not conspire to make you upgrade by withholding software development effort. No peripherals manufacturer is in a position to treat its customers that poorly. I realize nothing I say will convince anyone who wants to believe this, so I'll leave it at that.
|
|
|
|
|
integer-poet wrote: Either the manufacturer made you a promise of forward compatibility or it didn't, and either it kept that promise or it didn't. There is nothing else.
Um, backward compatibility? That's something else, which I think is actually on-topic to the survey.
Gary
|
|
|
|
|
Backward compatibility is when a manufacturer promises that given device works with an old OS, say Win2000.
Forward compatibility is when the manufacturer promises to support a device, say a camera, for X years, including future operating systems.
What's under discussion here is forward compatibility.
|
|
|
|
|
I actually agree with you about the manufacturer's not holding back technology. Unless they've some rather effective conspiracy, the naturally business sense is to be the first out and get the early and most lucritive sales (bigger $$$).
My impression doesn't rule out a conspiracy, but even OPEC usually can't keep its members under control long before someone tries to cash in on the gravey train by pumping a bit more (at least so far).
Like newspapers, with a rapidly changing industry such as we're in, there's monetary value in being the first to market.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
