Lexmark Monochrome Laser Complete Printer Reference (1.7 MB) - Page 173

Moving a disk from one printer to another, printer and install it in another printer

Page 173 highlights

Occasionally, however, circumstances can prevent a spooled job from printing. This may happen if: • An incoming print job is larger than the free space available in the job buffering partition. The printer deletes the job from the hard disk. • Someone selects Cancel Job from the Job Menu while a job is being spooled. This flushes the current job. None of the remaining jobs on the disk or in the link buffers is deleted. They are printed after the printer resets. • A job stored on the disk never receives a correct End-of-Job command. If the Jam Recovery, Page Protect, and Collation features are normally set on in your standard printer configuration, they should be left on when job buffering is enabled. Otherwise, the job buffering code does not receive a correct End-of-Job command in the event of an error. The job is considered incomplete and is not printed. To flush jobs already stored on the disk, you must issue the appropriate NPA commands through MarkVision. You cannot delete jobs stored on the disk from the operator panel. Moving a disk from one printer to another Unlike the majority of printer settings, job buffering settings are stored directly on the hard disk, not in the printer's nonvolatile memory. Therefore, if you remove a disk from one printer and install it in another printer, the job buffering settings are automatically established for the new printer. Suppose, for example, that you set a 60% partition for job buffering and then enabled the function on the parallel and network ports. If you turn off the printer and transfer the disk to another printer, those settings automatically take effect on the new printer. The first printer no longer has job buffering enabled on any port. This means that if a printer fails, you can remove the hard disk, place the disk in another printer, and print the jobs that are stored on the disk. Managing memory 173

  • 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
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236

Managing memory
173
Occasionally, however, circumstances can prevent a spooled job from printing. This may
happen if:
An incoming print job is larger than the free space available in the job buffering
partition.
The printer deletes the job from the hard disk.
Someone selects Cancel Job from the Job Menu while a job is being spooled.
This flushes the current job. None of the remaining jobs on the disk or in the link
buffers is deleted. They are printed after the printer resets.
A job stored on the disk never receives a correct End-of-Job command.
If the Jam Recovery, Page Protect, and Collation features are normally set on in
your standard printer configuration, they should be left on when job buffering is
enabled. Otherwise, the job buffering code does not receive a correct End-of-Job
command in the event of an error. The job is considered incomplete and is not
printed.
To flush jobs already stored on the disk, you must issue the appropriate NPA commands
through MarkVision. You cannot delete jobs stored on the disk from the operator panel.
Moving a disk from one printer to another
Unlike the majority of printer settings, job buffering settings are stored directly on the hard
disk, not in the printer’s nonvolatile memory. Therefore, if you remove a disk from one
printer and install it in another printer, the job buffering settings are automatically estab-
lished for the new printer.
Suppose, for example, that you set a 60% partition for job buffering and then enabled the
function on the parallel and network ports. If you turn off the printer and transfer the disk
to another printer, those settings automatically take effect on the new printer. The first
printer no longer has job buffering enabled on any port.
This means that if a printer fails, you can remove the hard disk, place the disk in another
printer, and print the jobs that are stored on the disk.