Intel PRO/100 Setup Guide - Page 38

copy /b - drivers

Page 38 highlights

r The network may not be connected to the print server. Use ping from a UNIX workstation to check IP connectivity to the Netport print server's TCP/IP task. r If using proprint on an SCO, Solaris, UnixWare, or HP-UX host, the complete path may need to be defined to proprint. Make sure the lp_scrpt1 file specifies the correct and complete path to the proprint utility. Also make sure the job number is specified. The next-to-last line of lp_scrpt1 must read: (shell commands ...) | usr/intl/hupx/proprint 'basename $0' job=1 exit $ ? r If using proprint, program may not be working. Check it by printing a job from the command line without using the spooling system. r If using lpd without proprint and printing binary or PostScript files, you may be using the wrong queue name. Make sure the queue name is LPT1_PASSTHRU forASCII files. Queues fill up but nothing prints r Another print server may be servicing the queue. Select a different queue or change the queue that the other print server is using. r The printer may be off line or set for the wrong type of port (parallel or serial). Check the printer and ports. r The network may not be connected. Check the network connection. Can you print a test page? If you can, check the network connection between the workstation and the print server. Also check the connection at the hub or switch. r If the job appears to print but nothing comes out of the printer, the job may be going to a different printer. r The driver parameters may be incorrect. You may be trying to send a PostScript job to a non-PostScript printer or sending a non-PostScript job to a PostScript printer. Print job doesn't print correctly r May be using wrong printer driver. Make sure the printer driver is the right one for the printer. r May need to toggle the printer's auto sensing of PostScript print jobs. r A Postscript printer may be trying to print a non-PostScript job. Check the job and the printer. r If you are copying a graphics (binary) file to LPT1, you may have the wrong parameter setting. Use the /b parameter: Type: copy /b filename lpt1 36

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

36
r
The network may not be connected to the print server. Use ping from a
UNIX workstation to check IP connectivity to the Netport print
server’s TCP/IP task.
r
If using
proprint
on an SCO, Solaris, UnixWare, or HP-UX host, the
complete path may need to be defined to
proprint
.
Make sure the lp_scrpt1 file specifies the correct and complete path to
the
proprint
utility. Also make sure the job number is specified. The
next-to-last line of lp_scrpt1 must read:
(shell commands ...) |
usr/intl/hupx/proprint ‘basename $0’ job=1 exit $ ?
r
If using
proprint
, program may not be working. Check it by printing a
job from the command line without using the spooling system.
r
If using
lpd
without
proprint
and printing binary or PostScript files,
you may be using the wrong queue name. Make sure the queue name
is LPT1_PASSTHRU for ASCII files.
Queues fill up but nothing prints
r
Another print server may be servicing the queue. Select a different
queue or change the queue that the other print server is using.
r
The printer may be off line or set for the wrong type of port (parallel or
serial). Check the printer and ports.
r
The network may not be connected. Check the network connection.
Can you print a test page? If you can, check the network connection
between the workstation and the print server. Also check the
connection at the hub or switch.
r
If the job appears to print but nothing comes out of the printer, the job
may be going to a different printer.
r
The driver parameters may be incorrect. You may be trying to send a
PostScript job to a non-PostScript printer or sending a non-PostScript
job to a PostScript printer.
Print job doesn’t print correctly
r
May be using wrong printer driver. Make sure the printer driver is the
right one for the printer.
r
May need to toggle the printer’s auto sensing of PostScript print jobs.
r
A Postscript printer may be trying to print a non-PostScript job. Check
the job and the printer.
r
If you are copying a graphics (binary) file to LPT1, you may have the
wrong parameter setting. Use the /b parameter:
Type:
copy /b
filename
lpt1