XP printer driver woes

A

Arthur Entlich

It means that MS tested it to make sure it doesn't conflict with other
aspects of the MS OS and that it works with standard MS applications.

They don't write the drivers, but they do troubleshoot them if they
break MS software.

The driver being signed also means it will operate in a certain manner
in the OS in regard to installation and OS awareness, and that it can be
included in an out of box version of the OS.

Art

So what does the m$ signed driver mean? and why does windows warn about using
an unsigned driver?

["Followup-To:" header set to comp.periphs.printers.]
MS does not write drivers for 3rd party hardware vendors products. It is up
to HP etc to provide drivers.
 
A

Arthur Entlich

Your argument is mainly with the manufacturers. It is not MS part to
make the drivers or to directly support them.

However, I think it might make sense to suggest that MS consider
obligating the manufacturers to supporting certain peripherals for X
years if they are going to be considered "Windows authorized" or "Vista
Authorized" peripherals.

The major fault however, is with the manufacturers, who love seeing
their equipment become obsolete. However, in the case of printers, some
are begining to understand that they make no money on printer sales
anyway, and the longer the printer is in service, the more they *MAY*
make on consumables, however, the big problem is the cost of writing new
drivers.

Now, having absolved MS, I will say this... there such be a way to patch
drivers so they can operate under new operating systems with a "bridge"
software in some manner. I'm not a coder, but it seems to me, even if
it slows the peripheral down somewhat, that there has to be a way to
insert a translator between the old driver and the new OS, and have them
able to understand the calls made by the other an that, it seems falls
back into MS's court.

Art


["Followup-To:" header set to comp.periphs.printers.]
MS does not write drivers for 3rd party hardware vendors products. It is up
to HP etc to provide drivers.


So the mfrs couldn't care less about drivers for legacy hardware,
let them die along with Win98 and the fat cats of Redmond are
quite happy to blame the mfrs when the drivers are crap.
Which is why MS is facing increasing pressure from open
source.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top