One reason I have read about is that there where problems with buggy
printservers that did not clear the out downloaded fonts and other
things.(especially these on a laserjet)
Setting the the filesize to something invalid would lead the software
to do a small soft reboot and clear up settings
On 12/11/05, Garance A Drosihn [EMAIL PROTECTED] wrote:
At 10:25 AM -0800 12/4/05, Greg Thomas wrote:
On 12/4/05, Steve Murdoch [EMAIL PROTECTED] wrote:
Any issues I had printing from XP went away when I enabled
LPR Byte counting in the LPR port settings.
Any ideas why that
At 10:25 AM -0800 12/4/05, Greg Thomas wrote:
On 12/4/05, Steve Murdoch [EMAIL PROTECTED] wrote:
Any issues I had printing from XP went away when I enabled
LPR Byte counting in the LPR port settings.
Any ideas why that is?
Apparently Windows (in general) does not like to keep a
Same issue when using the CUPS LPD daemon so it's not an LPD thing,
surprise surprise it looks like a Windows thing.
Greg Thomas wrote:
On 12/4/05, Steve Murdoch [EMAIL PROTECTED] wrote:
Any issues I had printing from XP went away when I enabled LPR Byte
counting in the LPR port settings.
Greg Thomas wrote:
Ok, I decided to switch from using a little Linksys 802.11b parallel
print server to using my OpenBSD box for printing to my one printer.
Printing locally works fine but I'm having trouble printing from XP.
[EMAIL PROTECTED]:/home/ethant# cat /etc/printcap
#
On 12/4/05, Steve Murdoch [EMAIL PROTECTED] wrote:
Any issues I had printing from XP went away when I enabled LPR Byte
counting in the LPR port settings.
Any ideas why that is?
Greg
On Fri, Dec 02, 2005 at 03:43:42PM -0500, Garance A Drosihn wrote:
At 6:19 PM + 12/2/05, Simon Slaytor wrote:
I seem to remember a problem when I was setting up the same
scenario as you using FreeBSD. When trying to print from a
Windows host using LPR/LPD the FBSD LPD daemon expects
Additional info. With this printcap on my OpenBSD laptop printing works fine:
[EMAIL PROTECTED]:/home/ethant# cat /etc/printcap
rp|remote line printer:\
:sf:sh:lp=:rm=grits:rp=lp:sd=/var/spool/output:lf=/var/log/lpd-errs:
So it appears to be an XP issue. Any suggestions for XP?
Greg
On
Greg Thomas wrote:
Ok, I decided to switch from using a little Linksys 802.11b parallel
print server to using my OpenBSD box for printing to my one printer.
Printing locally works fine but I'm having trouble printing from XP.
[EMAIL PROTECTED]:/home/ethant# cat /etc/printcap
# $OpenBSD:
On 12/2/05, Fred Crowson [EMAIL PROTECTED] wrote:
Greg Thomas wrote:
Ok, I decided to switch from using a little Linksys 802.11b parallel
print server to using my OpenBSD box for printing to my one printer.
Printing locally works fine but I'm having trouble printing from XP.
[EMAIL
Why not use CUPS?, with the CUPS LPD daemon, works like a charm for us.
Just enable RAW and LPR Byte accounting on your Windows XP hosts. When
configuring the CUPS printer again choose a RAW device to ensure
straight pass through from your Windows PC to the printer.
I seem to remember a
At 6:19 PM + 12/2/05, Simon Slaytor wrote:
I seem to remember a problem when I was setting up the same
scenario as you using FreeBSD. When trying to print from a
Windows host using LPR/LPD the FBSD LPD daemon expects
connections from a certain TCP/IP port on the connecting host,
but Windows
Ok, I decided to switch from using a little Linksys 802.11b parallel
print server to using my OpenBSD box for printing to my one printer.
Printing locally works fine but I'm having trouble printing from XP.
[EMAIL PROTECTED]:/home/ethant# cat /etc/printcap
# $OpenBSD: printcap,v 1.4
13 matches
Mail list logo
