The difference (and I'm not defending HP here) is that a print scheduler for your OS shouldn't even be *writable* by the install "wizard" for your printer.
Imagine an OS environment where a printer is a completely passive device that accepts requests to print onto paper. Imagine that it doesn't pong every device on the network, or every other printer on the network (remember appletalk?), and that there is no automatic "printer discovery". In my opinion, printer "discovery" should happen well before the time that the printer is installed. There's nothing to discover if you install the printer yourself. I didn't "discover" the printer attached to my PC when I plugged it in, I "discovered" it on the shelf of the store that I bought it from. If i'm a network administrator, I should be pretty much aware of when I plug a networked printer into the local network, and it seems to be a reasonable responsibility of mine to first make the decision about which machines should be able to print from it, and then to take the necessary steps to make that happen. Expecting an entire network of machines to do that job for me is not a particularly smart way to manage your network. s. _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
