I have experienced problems starting from Nevada build 42 (at the moment, I am using Nevada b55 developer edition and I have no info about subsequent releases). The problem is that, in many cases, a print request of a pdf or an ASCII document results in printing the postscript code, NOT the document. I tried to configure the printers both with and without PPD files; in both cases the configuration process seems to be ok: no error messages or warnings appear, and the lpstat command shows that printers are enabled and available. The following was the set of commands I run to configure a network printer (in such a case an HP Laserjet 2300, for which there is a PPD file (and it worked in Solaris 10, Nevada 24 and other releases)) :
% /usr/sbin/lpadmin -p hp2300 -s localhost -v /dev/null -m netstandard_foomatic -A none -n /usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_2300-Postscript.ppd.gz -o dest=172.16.3.47:9100 -o protocol=tcp -o banner=never -I postscript -u allow:all % /usr/sbin/lpadmin -p hp2300 -D "prova" % /usr/sbin/lpadmin -d hp2300 % /usr/bin/enable hp2300 % /usr/sbin/accept hp2300 I hope that the Solaris printing group is able to quickly resolve the many printing problems affecting newer Nevada releases, since they greatly discourage users and developers from using such platforms. Thanks/g.s This message posted from opensolaris.org
