From 2e2a5d50eb0fcbfdab14e56d6150a1bd35d57f28 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Wed, 13 Nov 2002 15:34:49 +0000 Subject: Some more doc updates: - make - update status of docs document - move security_level to 'type of installation' part (This used to be commit 11ad39398e077c3901e63f31bcc6efb223854357) --- docs/htmldocs/printing.html | 104 ++++++++++++++++++++++---------------------- 1 file changed, 52 insertions(+), 52 deletions(-) (limited to 'docs/htmldocs/printing.html') diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 5f054e1fda..b2b893afec 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -11,13 +11,13 @@ TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html">NextChapter 14. Printing SupportChapter 15. Printing Support

14.1. Introduction

15.1. Introduction

Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -163,9 +163,9 @@ CLASS="SECT1" >

14.2. Configuration

15.2. Configuration

14.2.1. Creating [print$]

15.2.1. Creating [print$]

In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -452,9 +452,9 @@ CLASS="SECT2" >

14.2.2. Setting Drivers for Existing Printers

15.2.2. Setting Drivers for Existing Printers

The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -524,9 +524,9 @@ CLASS="SECT2" >

14.2.3. Support a large number of printers

15.2.3. Support a large number of printers

One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -590,9 +590,9 @@ CLASS="SECT2" >

14.2.4. Adding New Printers via the Windows NT APW

15.2.4. Adding New Printers via the Windows NT APW

By default, Samba offers all printer shares defined in

14.2.5. Samba and Printer Ports

15.2.5. Samba and Printer Ports

Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -796,9 +796,9 @@ CLASS="SECT1" >

14.3. The Imprints Toolset

15.3. The Imprints Toolset

The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -814,9 +814,9 @@ CLASS="SECT2" >

14.3.1. What is Imprints?

15.3.1. What is Imprints?

Imprints is a collection of tools for supporting the goals of

14.3.2. Creating Printer Driver Packages

15.3.2. Creating Printer Driver Packages

The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -862,9 +862,9 @@ CLASS="SECT2" >

14.3.3. The Imprints server

15.3.3. The Imprints server

The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -886,9 +886,9 @@ CLASS="SECT2" >

14.3.4. The Installation Client

15.3.4. The Installation Client

More information regarding the Imprints installation client is available in the

14.4. Diagnosis

15.4. Diagnosis

14.4.1. Introduction

15.4.1. Introduction

This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -1063,9 +1063,9 @@ CLASS="SECT2" >

14.4.2. Debugging printer problems

15.4.2. Debugging printer problems

One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -1120,9 +1120,9 @@ CLASS="SECT2" >

14.4.3. What printers do I have?

15.4.3. What printers do I have?

You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -1149,9 +1149,9 @@ CLASS="SECT2" >

14.4.4. Setting up printcap and print servers

15.4.4. Setting up printcap and print servers

You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -1233,9 +1233,9 @@ CLASS="SECT2" >

14.4.5. Job sent, no output

15.4.5. Job sent, no output

This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -1278,9 +1278,9 @@ CLASS="SECT2" >

14.4.6. Job sent, strange output

15.4.6. Job sent, strange output

Once you have the job printing, you can then start worrying about making it print nicely.

14.4.7. Raw PostScript printed

15.4.7. Raw PostScript printed

This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -1339,9 +1339,9 @@ CLASS="SECT2" >

14.4.8. Advanced Printing

15.4.8. Advanced Printing

Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -1355,9 +1355,9 @@ CLASS="SECT2" >

14.4.9. Real debugging

15.4.9. Real debugging

If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.

NextUpSecurity levelsUnified Logons between Windows NT and UNIX using Winbind