home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- Path: sparky!uunet!dcatlas!drewo
- From: drewo@dcatlas.dot.gov (Andrew R. Orndorff)
- Subject: LPD client problems
- Message-ID: <1992Nov20.121155.22770@dcatlas.dot.gov>
- Organization: U.S Dept. of Transportation
- X-Newsreader: TIN [version 1.1 PL6]
- Date: Fri, 20 Nov 1992 12:11:55 GMT
- Lines: 46
-
-
- We're using the LPD client to provide print services from our
- cluster to printers available via a Novell server running Novell's NFS
- product. So far, things have been working fairly well, with the following
- exceptions:
-
- a) We're able to turn off burst pages, trailers, and flag
- pages on the Novell side of the connection, but do not
- seem to be able to do so from the VMS side.
-
- We've tried altering the way in which the queues are
- initialized, tried 'setting' the '/separate' and
- '/default' options after the queue has been initialized,
- and have even looked at the USER_LPD_CLIENT.C code in
- the [.Examples] directory, but to no avail.
-
- Is there some straightfoward way that we can enable the
- control of burst/flag/trailers from the VMS side - or
- turn them off altogether?
-
- b) Similary, I understand that LPD relies on the print server
- performing all of the filtering and other print options, but
- are there any plans to extend the MULTINET LPD client services
- beyond their current capabilities?
-
- Don't get me wrong, I'm not griping - it just would be nice to
- have a more flexible environment.
-
-
- Our current environment is 'OpenVMS' v5.5-2, Multinet v3.1d,
- an HP IIIsi printer with the Novell IPX/SPX network option, and device
- control libraries attached to the LPD client print queues (we at least got
- those straightened out)
-
- Any help or information would be much appreciated.
-
- Thanks.
-
- Andrew Orndorff
-
- NHTSA Data Center
-
- Internet: dcatlas!zeus.dot.gov!drewo@uunet.uu.net
- UUCP: uuent!dcatlas!zeus.dot.gov!drewo
-
-
-