Any ideas?
For anyone familiar with Samba and Windows printing I need SCO to keep it's
hands off of the data being sent to the printer--it should simply act as a
middle-man.
Regards, Dustin
--
Dustin Puryear <$email = "dpuryear"."@usa.net";>
Integrate Linux Solutions into Your Windows Network
- http://www.prima-tech.com/integrate-linux
>Has anyone been able to successfully print to a HP Laserjet III attached to a
>SCO OSR5 machine via Samba from a Windows client? I've tried both the
>'standard' and 'dumb' printer types and neither seems to work. I think that SCO
>is introducing some of it's own formatting into the process unfortunately. We
>can successfully print to an HP Laserjet 4 using the same process however.
Sure. My office printer is HP LaserJet III that's attached via a
parallel port to an 8 way parallel port switch. This allows me to test
various printing configuration from something like 8ea machines in the
office. It works just fine from Windoze.
Thank you for not specifying any versions of software, what application
is doing the printing, or precisely what fails when you try to print to
the HPIII. This allows me to guess, be vague, and generalize, which is
considerably less work than offering specifics. However, it's Chistmas
and I'm suppose to be nice today.
See:
http://us1.samba.org/samba/ftp/docs/htmldocs/using_samba/ch07_01.html#s1
for some clues as to how to setup SAMBA for printing.
See the various scripts in /usr/spool/lp/admin/lp/interfaces for command
line options. For unformatted printing try:
[HP3]
printable = yes
print command = lp -dname_of_printer -oraw %s
printer = lp
printing = SYSV
read only = yes
guest ok = yes
This assumes that you're using one of the "laserjet" spooler scripts
which knows about the "raw" option.
However, my guess is that if whatever you're doing works with the HP4,
but not with the HP3, you have some kind of formatting going on at the
Windoze client. Probably the Windoze printer driver is configured for an
HP4 and not an HP3. If your unspecified failure is simply being unable
to print anything to the HP3, check that the HP3 I/O port settings are
set to parallel, and not serial.
>Any ideas?
Oh-oh. Don't let Tony L. see this.
>For anyone familiar with Samba and Windows printing I need SCO to keep it's
>hands off of the data being sent to the printer--it should simply act as a
>middle-man.
Are you *SURE* that's the problem? Have you captured the output by
disabling the printer and looked at whatever is sitting in the spool
directory? Is it what you want? If not, how is it different? Any
chance it's PCL(something) which the HP4 supports but the HP3 does not?
--
Jeff Liebermann je...@comix.santa-cruz.ca.us
150 Felker St #D Santa Cruz CA 95060
831-421-6491 pager 831-429-1240 fax
http://www.cruzio.com/~jeffl/sco/ SCO stuff
| Has anyone been able to successfully print to a HP Laserjet III
| attached to a SCO OSR5 machine via Samba from a Windows client? I've
| tried both the 'standard' and 'dumb' printer types and neither seems
| to work. I think that SCO is introducing some of it's own formatting
| into the process unfortunately. We can successfully print to an HP
| Laserjet 4 using the same process however.
|
| Any ideas?
Ideas? You want ideas? How about some from you?. E.g.:
Any information from you to explain what "nothing seems to work" means?
Any information from you about your printer interface script?
--
JP
It pleases me to think
that your holidays are
rosy and bright and lovely.
I fail to connect any dots between cause and effect in that statement.
:-)
>Jeff Liebermann propounded (on Mon, Dec 25, 2000 at 02:08:12PM -0800):
>| However, it's Christmas and I'm suppose to be nice today.
>
>I fail to connect any dots between cause and effect in that statement.
>:-)
It's my guilty conscience. T'is the season to be jolly, and I've got a
cold, some irate customers, a 50% dead water heater, and a pile of repair
jobs that won't fix themselves. Probably karma failure. I figger that
if I can't be jolly for the season, at least I can try to be nice for one
day. Therefore, I resisted the temptation to repost my recently posted
checklist of things I hate about usenet news questions, and merely
bludgeon out a suitable answer, but without the usual vitriolic rant.
On the fourth day of Hannukah, my time-share cat tried to burn down the
house by batting at the candles. Anyone have a good recipe for cat?
Some more drivel on the HPIII and the various PCL versions (that I can
never seem to get straight).
http://www.printerworks.com/Catalogs/SX-Catalog/SX-HP_LaserJet-III.html
The HPIII does PCL5. The HP4 does "Enhanced PCL5" whatever that means.
SCO never supplied anything beyond PCL4 so it's not the spooler script.
Therefore, if the unspecified print job works with an HP4, and nothing
changes on the OSR5 side, it should work with the HPIII. However, if
it's graphics or image dumps, the HPIII only does 300dpi, while the HP4
will do 600 dpi and are therefore incompatible.
The "dumb" script introduces nothing beyond possible headers and
a formfeed, both of which can be disabled. It is definitely NOT
introducing any formatting, fortunate or unfortunate. The
"standard" script is generally inappropriate for a laser printer.
You say neither seems to work, but you give us no clue what the
problem is. If I had to take a wild guess, I'd bet it's lack of
CRLF translation that is throwing you off, but who knows? Your
lack of information is unlikely to produce the ideas you request.
See http://pcunix.com/SCOFAQ/scotec7.html and if that doesn't
help you, come back with a more intelligently prepared post.
--
Tony Lawrence (to...@aplawrence.com)
SCO/Linux articles, help, book reviews, tests,
job listings and more : http://www.pcunix.com
'nuff said. Here is my problem:
I have a SCO OSR5 machine. A HP Laserjet III is attached to it via a serial
port. I can print from the OSR5 machine to the HP Laserjet III fine. I have
the printer configured as "dumb" (I have tried "standard" and "HP Laserjet"
as well in the tests that follows.)
I have Samba 2.0.7 running on the SCO OSR5 machine. I have a Samba print share
configured that points to the HP Laserjet III.
If I connect to the print share using smbclient and print a text file it
works. (Works: the text file is printed on the HP Laserjet III and is legible
on the printed page.)
I then configure a Windows client to use the print share using the HP Laserjet
III print driver. I then print the Windows "test page". The HP Laserjet III
then prints ONE page. The page contains the appropriate text, in the proper size
and proportions, but the graphics are gibberish.
Next, I try to print to the same network printer a Word 97 document containing
the text "I am a test". The printer prints ONE page. There is no legible text on
the page--it is a line of gibberish.
I then change the driver Windows is using for the network printer from HP
Laserjet III to simply HP Laserjet.
I get similar results when repeating my tests from Windows.
If I connect the same HP Laserjet III directly to the Windows client then the
HP Laserjet III driver works, and all print-outs are correct.
My question: if the "dumb" print filter doesn't add or remove any formatting
codes to the print job why is this not working?
>On Tue, 26 Dec 2000 06:10:41 -0500, Tony Lawrence
><to...@aplawrence.com> wrote:
>>> Has anyone been able to successfully print to a HP Laserjet III
>>>attached to a SCO OSR5 machine via Samba from a Windows client?
>>>I've tried both the 'standard' and 'dumb' printer types and
>>>neither seems to work. I think that SCO is introducing some of
>>>it's own formatting into the process unfortunately
>>You say neither seems to work, but you give us no clue what the
>>problem is. If I had to take a wild guess, I'd bet it's lack of
>>CRLF translation that is throwing you off, but who knows? Your
>>lack of information is unlikely to produce the ideas you request.
>'nuff said. Here is my problem:
....
>My question: if the "dumb" print filter doesn't add or remove any
>formatting codes to the print job why is this not working?
How about using the HP Laserjet III 'filter' and use the -o raw
option? Since you say it's a graphics printing problem, that's
what you typically use 'raw' for.
Bill
--
Bill Vermillion - bv @ wjv . com
I'd guess you are doing crnl mapping somewhere- but that wouldn't
be in the dumb filter by default.
Try just "cat /etc/passwd > /dev/tty1a" (or whatever the serial
port is). If that stair-steps, then you have crnl mapping
somewhere in the print setup (which would screw up graphics but
not text).
>> My question: if the "dumb" print filter doesn't add or remove any
>> formatting codes to the print job why is this not working?
>I'd guess you are doing crnl mapping somewhere- but that wouldn't
>be in the dumb filter by default.
>Try just "cat /etc/passwd > /dev/tty1a" (or whatever the serial
>port is). If that stair-steps, then you have crnl mapping
>somewhere in the print setup (which would screw up graphics but
>not text).
There are three line termination options in the HP also. There is
also a line wrap-option.
I thought he was having problems printing graphics and not
stairsteps.
>I have a SCO OSR5 machine. A HP Laserjet III is attached to it via a serial
>port.
Did you check if your serial port flow control is working? Printing
short text files is not a good test as it takes many pages to overflow
the serial port handshaking. Check the OSR5 printer script line that
starts with "stty" matches your illusion of flow control (xon/xoff or
cts/rts). I inscribed a short rant on serial printing at:
http://www.cruzio.com/~jeffl/sco/serial_print.txt
which is mostly targetted at Digiboard intelligent serial cards, but
applies to most others. My favorite fast test is to start a long print
job and just punch the "on line" button on and off a few times at about
10 second intervals. If the print job looks like garbage, it's not
working.
>If I connect to the print share using smbclient and print a text file it
>works. (Works: the text file is printed on the HP Laserjet III and is legible
>on the printed page.)
Is that a SHORT text file or a LONG text file? At 9600 baud, I *guess*
you can shovel about 4ea 1K text pages at the printer without worrying
about flow control.
>I then configure a Windows client to use the print share using the HP Laserjet
>III print driver. I then print the Windows "test page". The HP Laserjet III
>then prints ONE page. The page contains the appropriate text, in the proper size
>and proportions, but the graphics are gibberish.
I captured the ouput of my Windoze 98 test page. The PCL is fairly easy
to read. It first prints all the text on the page, followed by the
graphics. If it makes it through the text without a flow control
problem, but overflows in the middle of the graphic, we have a situation
similar to your symptoms.
>Next, I try to print to the same network printer a Word 97 document containing
>the text "I am a test". The printer prints ONE page. There is no legible text on
>the page--it is a line of gibberish.
MS Turd 97 sends lots of font information before printing the actual
text. The gibberish is actually the font loading or page formatting
information gone awry.
>If I connect the same HP Laserjet III directly to the Windows client then the
>HP Laserjet III driver works, and all print-outs are correct.
Did you connect it to the serial port on the Windoze box or the parallel?
If you connected it to the serial port, what did you set the printer
properties flow control settings? If you turn off flow control, can you
reproduce the symptoms on the Windoze serial port? My guess is that you
can.
>My question: if the "dumb" print filter doesn't add or remove any formatting
>codes to the print job why is this not working?
Serial flow control. Try switching the HP3 to the OSR5 parallel port and
see if the problem magically goes away.
Wouldn't the HP show the error on its front panel?
Correct. Mapping CRNL in the interface will screw up graphics
and not affect text. Mapping it within the printer itself does
not, the difference being that stty or lponlcr doesn't know what
really is text and what isn't and the HP firmware does.
All this is true unless my brain is completely out to lunch this
weekend :-)
>> In article <3A4E324E...@aplawrence.com>,
>> Tony Lawrence <to...@aplawrence.com> wrote:
>> >Dustin Puryear wrote:
>> >> My question: if the "dumb" print filter doesn't add or remove any
>> >> formatting codes to the print job why is this not working?
>> >I'd guess you are doing crnl mapping somewhere- but that wouldn't
>> >be in the dumb filter by default.
>> >Try just "cat /etc/passwd > /dev/tty1a" (or whatever the serial
>> >port is). If that stair-steps, then you have crnl mapping
>> >somewhere in the print setup (which would screw up graphics but
>> >not text).
>> There are three line termination options in the HP also. There is
>> also a line wrap-option.
>> I thought he was having problems printing graphics and not
>> stairsteps.
>Correct. Mapping CRNL in the interface will screw up graphics
>and not affect text. Mapping it within the printer itself does
>not, the difference being that stty or lponlcr doesn't know what
>really is text and what isn't and the HP firmware does.
>All this is true unless my brain is completely out to lunch this
>weekend :-)
Wouldn't setting the -o raw option cure his problem? Thanks for
the heads-up on the CRNL screwing up graphics.
>Jeff Liebermann wrote:
>>
>> On Sat, 30 Dec 2000 03:32:53 GMT, dpur...@no.spam.please (Dustin
>> Puryear) wrote:
>>
>> >I have a SCO OSR5 machine. A HP Laserjet III is attached to it via a serial
>> >port.
>>
>> Did you check if your serial port flow control is working?
>
>Wouldn't the HP show the error on its front panel?
Good point. I'm not sure. As I vaguely recall (and not having manual
handy), the "page protect" feature also allows the printer to continue by
itself after an error. What I can't remember is whether you get an
Error 20 message but it continues printing, or whether it just stops.
Methinks it continues printing and recovers by itself if "page protect"
is on or set to "auto". There's also the "auto continue" setting which
methinks allows automatic error recovery. My last remaining HP3 is in
the office, I'm at home celebrating the end of the year by frantically
getting my bookkeeping together, and will not be able to check until next
year.
>Wouldn't setting the -o raw option cure his problem? Thanks for
>the heads-up on the CRNL screwing up graphics.
Only on printer interfaces that know about the -o raw option.
The HPLaserJet interface certainly knows about raw, but the dumb and
crnlmap interfaces do not recognize this option.
Looking at the actual interface scripts in:
/var/spool/lp/model/
The "dumb" script goes through the default filter LPCAT and then uses
lp.cat (same as cat but with an ending buffer flush) to directly dump
whatever you feed it to the printer. This is probably the correct
script for unbutchered output. Looking at the crnlmap script, it looks
almost identical. Unless I missed something, I don't see anything in
either script that would result in the scripts modifying the print data.
(Note that I suggested that he try HPLaserJet interface with the -o raw
option in my first posting on this problem).
On my office system, that uses an HP3, is running Samba 1.9PL20(??),
prints nicely from my Windoze 98 SE box, and does not screw up, uses the
HPLaserJet interface, and the -o raw option in the SAMBA config.
However, I'm using the parallel port, not the serial on the printer and
OSR5 box.
>>Wouldn't setting the -o raw option cure his problem? Thanks for
>>the heads-up on the CRNL screwing up graphics.
>Only on printer interfaces that know about the -o raw option.
>The HPLaserJet interface certainly knows about raw, but the dumb and
>crnlmap interfaces do not recognize this option.
About a 1/2 dozen repies ago I asked him the question why he
didn't use the HP interfaces and set -o raw. No reply on that one.
>(Note that I suggested that he try HPLaserJet interface with the -o raw
>option in my first posting on this problem).
So did I. I guess they don't trust us anymore.
I am not sure how to do this. I ran 'scoadmin printer' and didn't see the
option to use "raw" printing. I also viewed /etc/printcap and viewed it's
manpage for any OSR5-specific extensions.
I would think that since you are saying use '-raw' and not 'raw' that I should
be using it as an option to the "filter", but I am at a loss how.
Would you mind explaining it to me, or directing me to the approriate
documentation? I don't see it in the SCO OSR5 hardcopy or online system docs.
Oh.. so I need to override the Samba lpr statement with 'lpr -o raw ...',
correct? That would answer my previous post.
Actually, the whole '-o raw' dealie came from everyone at approximately the
same time. So to imply that I ignored them is incorrect.
Now, the fact that I am only now replying is certainly in bad taste, but..
Well, if were a serial port flow control issue then printing from our
OSR5-based applications should be affected as well, but they aren't. We can
print very large documents (100+ pages) from within SCO OSR5, but via Samba
I am having problems.
>>My question: if the "dumb" print filter doesn't add or remove any formatting
>>codes to the print job why is this not working?
>
>Serial flow control. Try switching the HP3 to the OSR5 parallel port and
>see if the problem magically goes away.
I can do this test, but I honestly do not believe it is flow control related.
As I mentioned, this problem only occurs when printing from a Windows
application via Samba. This indicates to me that it is a filter or filter
setting issue since Windows assumes it should do the print processing, rather
than the printer server/remote machine.
Let me know if you feel otherwise.
all you do in scoadmin is select the model "HPLaserJet" (or whatever other
model you see there that you want to try out)
to use the "-oraw" (not "raw", and not "-raw", do not presume we made
typos until you try it exactly as stated and it doesn't work) in smb.conf
where it says "lp <some stuff>" insert "-oraw" into the <some stuff>
here is a sample from my smb.conf on my linux box...
[global]
...
print command = lpr -r -P%p %s
...
here is the equivalent for osr5
[global]
...
print command = lp -d%p -oraw %s
...
note 2 things:
this print command can be added to to indavidual shares sections too, so
you can have something like:
[NEC P1200]
comment = NEC PinWriter P1200
path = /var/spool/samba
writeable = Yes
guest ok = Yes
printable = Yes
printer = nec
print command = lp -d%p -oraw,nff,b,12cpi,lq %s
and also the "print command =" line doesn't even show up by default
anywhere in smb.conf in some cases unless you want to modify it from it's
default behaviour.
I highly recommend enabling swat.
I've already regurgitated enough stuff that you could have read for
yourself by typing in "samba configuration" into any search engine, so I
leave it to you to do that and find out how one enables and uses swat.
--
Brian K. White http://www.squonk.net/users/linut
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
>>How about using the HP Laserjet III 'filter' and use the -o raw
>>option? Since you say it's a graphics printing problem, that's
>>what you typically use 'raw' for.
>I would think that since you are saying use '-raw' and not 'raw'
>that I should be using it as an option to the "filter", but I am at
>a loss how.
I did not say -raw. I said -o raw
As in lp -o raw -d HPBeast - along those lines.
>Would you mind explaining it to me, or directing me to the
>approriate documentation? I don't see it in the SCO OSR5 hardcopy
>or online system docs.
-o is the start of the options for the interface script. Look at
one of the interface scripts and you'll see all the options
available, such as for landscape, compressed print, etc.
The raw option just passes the data stream through.
Jesus, everyone is giving different syntaxes. Someone just said it was -oraw.
Anyway, I did try '-o raw' (the '-raw' was bad typing by me), and it didn't
seem to fix the problem. I'll have to dig a little deeper and return with a
better summary of the results from the fixes that were suggested.
>>Would you mind explaining it to me, or directing me to the
>>approriate documentation? I don't see it in the SCO OSR5 hardcopy
>>or online system docs.
>
>-o is the start of the options for the interface script. Look at
>one of the interface scripts and you'll see all the options
>available, such as for landscape, compressed print, etc.
>
>The raw option just passes the data stream through.
Thanks!
> Jesus, everyone is giving different syntaxes. Someone just said it was -oraw.
> Anyway, I did try '-o raw' (the '-raw' was bad typing by me), and it didn't
> seem to fix the problem. I'll have to dig a little deeper and return with a
> better summary of the results from the fixes that were suggested.
Stop looking for the magic incantation and spend the effort to
UNDERSTAND.
See http://pcunix.com/SCOFAQ/scotec7.html and read "man lp" and
the related pages..