Sharp Ud3 Pcl6 Driver Download

[Lacy Tortelli]

Ithink you are on the right path with the firmware idea. The last

MSGID I got from the log showed that it could not connect via the SNMP

server. I created an OUTQ to bypass the SNMP portion of the printer

and it worked. Apparently, the issue resides with the SNMP buffer not

clearing out correctly on the printer. I'm going back to Sharp and

looking for a firmware update. Thanks for all of your help!

The mfrtypmdl merely controls the datastream generated and sent to the

printer. It does not control how the writer communicates with the printer.Communications with the printer is controlled by the sysdrvpgm

parameter. Since you are using the *IBMSNMPDRV, the problem is with use

of the SNMP communications to get status.You could try configuring the printer using the *IBMPJLDRV to see if

that works. Its not quite as good from an error recovery/error

reporting point of view, but may get you around the problem.Another option may be to try the *IBMIPPDRV driver. This would use the

IPP 1.1 protocol. This has a lesser chance of working since many

printer say they support IPP 1.0 or even 1.1, but in reality didn't

support all the required options of IPP 1.0 and 1.1 (i.e. they did only

what was required to work with M$).The last option, and likely the one that will always work, is the remote

writer. This comes with many limitations and a lot less error reporting

information. Some still want to have a printer device and have used the

TSPLPRD printer driver example program.If you can get sharp to get you a firmware fix to sovle the snmp

problem, that is still your best choice. The alternatives mentioned

above could be a good temporary workaround. Or permanent if Sharp won't

fix it.

--

Rodney A Johnson

Working on a new project. Former technical team Lead for i5/OS (AS/400)

Spool

Dept 33A

IBM Rochester, MinnesotaThe contents of this message express only the sender's opinion.

This message does not necessarily reflect the policy or views of

my employer, IBM. All responsibility for the statements

made in this Usenet posting resides solely and completely with the

sender.

3a8082e126