HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Adding a Line printer.
Operating System - HP-UX
1827943
Members
2313
Online
109973
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2001 12:47 PM
08-13-2001 12:47 PM
Adding a Line printer.
I've been trying to work this issue with a new line printer for our HP-UX 10.20 Server, and I can't get the printer to print once I send the print to the Line Printer on the Unix side. But it will print to the printer on the Windows NT side. We have the printer set up as a network printer going throug a Print Server using an Windows NT OS as it's base. The new line Printer is a Talley 6101T with a built in NIC card and thus not needing the use of a JetAdmin direct box. I've checked the HP-UX files such as the /etc/hosts and /etc/services and it all seems to check out to include the new IP address of the printer to the /etc/hosts file. I've added the printer in alright on the Printer and Plotters side of the SAM and ensured the Printer name from the NT side is the same as on the HP-UX side as well. The Pintouts will print a garbled one line of text and then form feed one page up. Then the printer will stop as if it has printed out the text completed.
Is there anyone out there who could possibly help me out on this one?
Is there anyone out there who could possibly help me out on this one?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2001 04:02 PM
08-13-2001 04:02 PM
Re: Adding a Line printer.
JetDirect support includes local processing of special files like ASCII. All other network adapters I've seen implement a form of the remote lp daemon (rlp). HP-UX, like other flavors of Unix, stores ASCII files as strings followed by the LF character and most printers will do exactly as told: text LF text LF...
which on the paper looks like a stairstep effect. This is correct behavior but not desired. With local and JetDirect printers, the printer script handles the conversion by adding CR to every LF, but no such conversion will occur on other systems like Windows or network cards.
Start by adding the printer with SAM as a remote printer, not a network printer. You will need to determine the network card's internal printer name. JetDirect has the two names: text and raw. Adding a remote printer requires the local queue name, the remote computername (or IP address of the network card) and the internal printer name.
Once SAM has added the printer, you can try printing a plain ASCII file with the ux2dos command. It will add the necessary CR to each LF.
Bill Hassell, sysadmin
which on the paper looks like a stairstep effect. This is correct behavior but not desired. With local and JetDirect printers, the printer script handles the conversion by adding CR to every LF, but no such conversion will occur on other systems like Windows or network cards.
Start by adding the printer with SAM as a remote printer, not a network printer. You will need to determine the network card's internal printer name. JetDirect has the two names: text and raw. Adding a remote printer requires the local queue name, the remote computername (or IP address of the network card) and the internal printer name.
Once SAM has added the printer, you can try printing a plain ASCII file with the ux2dos command. It will add the necessary CR to each LF.
Bill Hassell, sysadmin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP