To read all comments associated with this story, please click here.
Probably at the point of installation, Vista did not know that this was a printer driver in particular that was installing and not some other piece of software. For most general end-user software (i.e. the MyPrettyAccountingPackage's of the world), this redirection will make them work perfectly fine without requiring admin rights on the box. A combination of unlucky circumstances made it do the exact opposite on this customer's machine and that's unfortunate.
It's hard to be sure something will work unless it's actually tried. Bob Colwell, the chief engineer of the P6 and Pentium IV, had the extremely applicable motto, "If it ain't tested, then it's broken." By the time WinXP went through two years of its life, things were pretty well tested throughout the Windows ecosystem, except for those hardware items that were discontinued. Vista has been generally available for 18 months and I'd be fairly confident about buying a new piece of hardware and having it work on Vista today. Perhaps the main failing here was the lack of great diagnostics about why the install was failing. Maybe such diagnostics were available and the Windows Test guy was able to use them... there are just some areas where novices can't quite solve the problem without help.




Member since:
2005-07-13
I thought hardware drivers had to be certified to install in Vista (not running it may be totally wrong). Surely when the installer tried writing the driver files, or modifying the Drivers section in the Registry that Vista could have said NO instead of SILENTLY putting them somewhere else.
If Vista had said no and the installer then errored and backed out, the guy would have looked for new drivers then and there. The OS (Vista in this case) IS at fault, it is the silent redirection of DETECTABLE driver files and config that caused the issue.