Lantronix MPS100 EPS Reference Manual - Page 111

Troubleshooting Macintosh Printing

Page 111 highlights

AppleTalk Host Setup Troubleshooting Macintosh Printing Files containing embedded bitmap graphics may not print correctly even if the text surrounding the graphics does. This is because the bitmaps are actually binary data in this case, and binary data cannot be printed via serial or parallel interfaces. Most major application packages have provisions to print using either binary PostScript (for printers connected to the network via LocalTalk) or hex PostScript (for printers connected to the network via a serial or parallel port). If the application you're using does not have this provision, contact the application vendor to see if there is an upgrade patch that adds this functionality. 10.3 Troubleshooting Macintosh Printing AppleTalk printing is easy to set up, but can be hard to debug. Since the Macintosh is expecting PostScript replies from the print device, you cannot just attach a terminal to the Server and watch the output. Also, there is no way to "connect" to the Server port and talk to the printer via AppleTalk-you need to do so via LAT or Telnet. 10.3.1 General Troubleshooting Table 10-1 shows a few common problems that you may encounter. When possible, try to get an error message from the printer to track down the problem (see Error Messages on page 10-4). Table 10-1: Troubleshooting Macintosh Printing Problem Possible Cause Explanation/Remedy Special characters or bitmaps don't print correctly. The printer is config- Use the Set/Define Port Character Size command to ured for 7-bit characters change the character size to 8-bits. rather than 8-bit. The print job doesn't print. The printer is listening Examine the banner page printed at the start of the print to the wrong port (for job, if any. It will typically tell whether the printer is lisexample, it may be lis- tening to LocalTalk or the serial port or both, and will tening to the serial port show the serial settings. Also watch the input/output when the job is coming counters in the Show Port Counters display. from LocalTalk). A printer set to LocalTalk will not send errors, replies, or acknowledgments to the Server. However, a serial line analyzer could be used to view this information. Typically DIP switches are used to force the printer to use the serial port. The print job doesn't The printer is not print receiving data. Most printers blink an LED as they receive data to show that they are getting something from the Server/ Macintosh. If the LED is not blinking, try to get an error message from the printer (see Error Messages on page 10-4). When the job is finished and the printer is idle, the LED is typically solidly lit. 10-3

  • 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
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223

AppleTalk Host Setup
Troubleshooting Macintosh Printing
10-
3
Files containing embedded bitmap graphics may not print correctly even if the text surrounding the graphics
does. This is because the bitmaps are actually binary data in this case, and binary data cannot be printed via
serial or parallel interfaces. Most major application packages have provisions to print using either
binary
PostScript
(for printers connected to the network via LocalTalk) or
hex PostScript
(for printers connected
to the network via a serial or parallel port). If the application you’re using does not have this provision,
contact the application vendor to see if there is an upgrade patch that adds this functionality.
10.3
Troubleshooting Macintosh Printing
AppleTalk printing is easy to set up, but can be hard to debug. Since the Macintosh is expecting PostScript
replies from the print device, you cannot just attach a terminal to the Server and watch the output. Also, there
is no way to “connect” to the Server port and talk to the printer via AppleTalk—you need to do so via LAT
or Telnet.
10.3.1
General Troubleshooting
Table 10-1 shows a few common problems that you may encounter. When possible, try to get an error
message from the printer to track down the problem (see
Error Messages
on page 10-4).
Table 10-1:
Troubleshooting Macintosh Printing
Problem
Possible Cause
Explanation/Remedy
Special characters or
bitmaps don’t print
correctly.
The printer is config-
ured for 7-bit characters
rather than 8-bit.
Use the
Set/Define Port Character Size
command to
change the character size to 8-bits.
The print job doesn’t
print.
The printer is listening
to the wrong port (for
example, it may be lis-
tening to the serial port
when the job is coming
from LocalTalk).
Examine the banner page printed at the start of the print
job, if any. It will typically tell whether the printer is lis-
tening to LocalTalk or the serial port or both, and will
show the serial settings. Also watch the input/output
counters in the Show Port Counters display.
A printer set to LocalTalk will not send errors, replies, or
acknowledgments to the Server. However, a serial line
analyzer could be used to view this information. Typically
DIP switches are used to force the printer to use the serial
port.
The print job doesn’t
print
The printer is not
receiving data.
Most printers blink an LED as they receive data to show
that they are getting something from the Server/ Macin-
tosh. If the LED is not blinking, try to get an error mes-
sage from the printer (see
Error Messages
on page 10-4).
When the job is finished and the printer is idle, the LED is
typically solidly lit.