SimulatePassThrough

  • Thread starter Thread starter Del
  • Start date Start date
D

Del

We have a UNIX app that when we print certain reports from
it will make the text really large. I was able to fix this
in Windows NT by adding the SimulatePassThrough entry in
the registry. We recently pruchased new computers with XP
pro and the printing issue popped up so I added the
SimulatePassThrough entry to the same regisrty key again.
With XP it did not resolve our printing problem. Does any
one have any suggestions on how to resolve my large print
problem when sending print jobs from a unix server /
program?
 
When the LPD service running in the XP system gets the first job to the
printer it will create 2 registry DWord values under
HKLM\System\CurrentControlSet\Control\Printer\Printers\"Printer
Name"\PrinterDriverData\
LpdPrinterDontDetect
LpdPrinterPassThrough
Both are set to 0

Change Passthrough to 1.

The article says stop and restart lpdsvc and spooler

KB article on this

http://support.microsoft.com/default.aspx?scid=kb;en-us;168457


--
Alan Morris

Microsoft Printing Team

http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Alan,

That's so close to my problem, but the cure didn't seem
to work. I have an XP Pro machine (SP1), an HP LaserJet
1300, and an SMC 7004BR print server. I installed both
the PCL and PS drivers off the HP CD (HP said to use
those, not the drivers from the MS site) and tested my
configuration on USB; it worked. Then I configured my
computer according to
http://www.smc.com/drivers_downloads/library/Barricade_XP_
LPRPrinting.pdf to get LPR printing working. That all
works, except that I'm getting Postscript or PCL source
on the paper, not the rendered page.

I tried a number of things to no avail before finding
that suggestion. I set the new value in the registry,
rebooted, and, lo and behold, I still got raw PS or
PCL. :-(

There are two things I didn't understand from your
message; perhaps they are key. First, you say XP will
create those values. I've never seen either of them,
even after having printed something (the unprocessed PS,
for example). Second, I didn't create the key
LpdPrinterDontDetect and set it to 0.

Any suggestions?

Thanks,

Bill

-----Original Message-----
When the LPD service running in the XP system gets the first job to the
printer it will create 2 registry DWord values under
HKLM\System\CurrentControlSet\Control\Printer\Printers\"P rinter
Name"\PrinterDriverData\
LpdPrinterDontDetect
LpdPrinterPassThrough
Both are set to 0

Change Passthrough to 1.

The article says stop and restart lpdsvc and spooler

KB article on this

http://support.microsoft.com/default.aspx?scid=kb;en- us;168457


--
Alan Morris

Microsoft Printing Team

http://support.microsoft.com/default.aspx?scid=fh; [ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.

Del said:
We have a UNIX app that when we print certain reports from
it will make the text really large. I was able to fix this
in Windows NT by adding the SimulatePassThrough entry in
the registry. We recently pruchased new computers with XP
pro and the printing issue popped up so I added the
SimulatePassThrough entry to the same regisrty key again.
With XP it did not resolve our printing problem. Does any
one have any suggestions on how to resolve my large print
problem when sending print jobs from a unix server /
program?
Click to expand...


.
Click to expand...
 
Are you using the LPD service that ships with XP?

If not, then none of these setting will work.

Do you have a Unix client that targets the XP systems shared printer.



--
Alan Morris

Microsoft Printing Team

http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.

Bill Harris said:
Alan,

That's so close to my problem, but the cure didn't seem
to work. I have an XP Pro machine (SP1), an HP LaserJet
1300, and an SMC 7004BR print server. I installed both
the PCL and PS drivers off the HP CD (HP said to use
those, not the drivers from the MS site) and tested my
configuration on USB; it worked. Then I configured my
computer according to
http://www.smc.com/drivers_downloads/library/Barricade_XP_
LPRPrinting.pdf to get LPR printing working. That all
works, except that I'm getting Postscript or PCL source
on the paper, not the rendered page.

I tried a number of things to no avail before finding
that suggestion. I set the new value in the registry,
rebooted, and, lo and behold, I still got raw PS or
PCL. :-(

There are two things I didn't understand from your
message; perhaps they are key. First, you say XP will
create those values. I've never seen either of them,
even after having printed something (the unprocessed PS,
for example). Second, I didn't create the key
LpdPrinterDontDetect and set it to 0.

Any suggestions?

Thanks,

Bill

-----Original Message-----
When the LPD service running in the XP system gets the first job to the
printer it will create 2 registry DWord values under
HKLM\System\CurrentControlSet\Control\Printer\Printers\"P rinter
Name"\PrinterDriverData\
LpdPrinterDontDetect
LpdPrinterPassThrough
Both are set to 0

Change Passthrough to 1.

The article says stop and restart lpdsvc and spooler

KB article on this

http://support.microsoft.com/default.aspx?scid=kb;en- us;168457


--
Alan Morris

Microsoft Printing Team

http://support.microsoft.com/default.aspx?scid=fh; [ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.

Del said:
We have a UNIX app that when we print certain reports from
it will make the text really large. I was able to fix this
in Windows NT by adding the SimulatePassThrough entry in
the registry. We recently pruchased new computers with XP
pro and the printing issue popped up so I added the
SimulatePassThrough entry to the same regisrty key again.
With XP it did not resolve our printing problem. Does any
one have any suggestions on how to resolve my large print
problem when sending print jobs from a unix server /
program?
Click to expand...


.
Click to expand...
Click to expand...
 
Alan Morris\(MSFT\) said:
Are you using the LPD service that ships with XP?

If not, then none of these setting will work.

Do you have a Unix client that targets the XP systems shared printer.
Click to expand...

I messed up and double-posted; I propose we stop this thread and move
anything pertinent to "LaserJet 1300 prints Postscript source on XP".
(I'm actually using the lpd inside a NAT router, or trying to.)

Thanks,

Bill
 
Back
Top