From owner-freebsd-questions Thu Apr 10 06:57:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA06536 for questions-outgoing; Thu, 10 Apr 1997 06:57:59 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA06531 for ; Thu, 10 Apr 1997 06:57:54 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id QAA01256; Thu, 10 Apr 1997 16:55:53 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma001254; Thu Apr 10 16:55:43 1997 Message-ID: <334CF14C.5DC8@barcode.co.il> Date: Thu, 10 Apr 1997 16:55:24 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: "Neil T. Mathison" CC: "Pariy, Semion" , questions@freebsd.org Subject: Re: FreeBSD -> NT40 -> printer References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Neil T. Mathison wrote: > > On Thu, 10 Apr 1997, Pariy, Semion wrote: > > > > > Hi! > > > > how can I install printer on FreeBSD 2.2 , if printer connected to > > computer with Windows NT40. FreeBSD and NT40 connected to local > > network? > > > > Semion Pariy > > > > I am struggling with this also. We are using NT 3.51 with it's TCP/IP > printing services (LPD daemon). The target printer is a HP Laserjet 4M. > printcap is set up for remote printing as per the handbook. However, > right now it only prints plain ASCII correctly. Even though the HP 4M > is suppose to switch to it's postscript personality automatically upon > seeing a postscript file, its is printed as text. Moreover, special > characters like backspace are not interpreted as such, but are displayed > as a 'garbage' character. > > The print spooler on the NT box is set up to treat the data as RAW, > which I assumed to mean to pass it through without screwing with it. > The lack of handling of the backspace character confirms that much. > However, why is a postscript file not recognized as such by the HP. > > Some NT guru mentioned that the NT LPD service required a control > character of (lower case l). I'm not certain what he meant by that, > and neither was he. He pulled it out of some book. Real easy. Send the jobs using lpr -l instead of plain lpr. I didn't have this problem with NT 3.51 (just with 4.0), but the symptoms you describe seem to indicate that this is indeed the cure. > > Anyway, I will need to experiment with filters to see if I can print > files other than as just plain text. I would be interested in finding > out what you discover. > > Regards, > > Neil Mathison Nadav