Within the UPD-specs are that the printer dynamically should be able to
configure/reconfigure the UPD-driver on the host-side. I.e, the printer
tells the printer driver how it is configured to relieve the end =
user/admin
person from doing this task and keep them out of trouble.
This dynamic configuration calls for a "configuration"-metalanguage to =
be
defined that the UPD/operating system can interpret.
It would be of equal of worth to be able to do configuration the other =
way
around. I.e configure the PRINTER through a standard metalanguage, =
things
like turning network protocolls on/off, set printer defaults and more.
Would it be impossible for you, or some other PWG group, to put into
your/their scope of work to define a standard "printer
configuration"-metalanguage that all printers could interpret. As it is =
now
it is a jungle. There are postscript snippets, vendor proprietary =
languages,
private SNMP MIBs, HTTP and other ways to configure the actual printer.
There could be a multiple of ways to send this configuration file to =
the
printer. Either do a copy over the parallell port or send the file over =
the
network via lpr, ftp or do a automatic download via bootp/tftp.
Kind regards Krister Sv=E4rd
Skandia Utdata Teknik Telefon: +46 8 788 28 87
S-103 50 STOCKHOLM Mobil: +46 70 689 28 87
E-mail: krister.svard@skandia.se
http://www.skandia.se