Lexmark MX826 Printer Languages and Interfaces Technical Reference - Page 131

Device search order, setfilenameextend, undefinedfilename, run, file, renamefile, status, eexec

Get Lexmark MX826 PDF manuals and user guides View all Lexmark MX826 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

Flash memory and hard disk 131 This occurs because the file name actually written is iconimage.data. When setfilenameextend is enabled (the default), all PostScript emulation file operators treat file name operands as filename.data; when disabled, they treat file name operands literally. If you receive unexpected undefinedfilename or similar errors, try toggling setfilenameextend and sending your print job again. Device search order If you are using the PostScript emulation operators run, file, renamefile, status, or eexec, then you do not need to specify the device. If you omit the device name, devices are searched in the default order: hard disk, and then flash memory. If the PostScript emulation code (myfile) (w) file is encountered, then the file on the hard disk is used. Note: Files cannot be created in ROM. If a device is not specified, then the operator deletefile searches only the first device in the default search order. Use the PostScript emulation operators devmount, devdismount to change the order. The order the devices are mounted determines the default search order. For example, if you want to place the disk device after the flash memory in the default search order, then use the following command sequence: (%disk%) devdismount (%disk%) devmount To change the order so the devices are searched as hard disk, flash memory, and then ROM, use the following PostScript emulation command sequence: (%rom%) devdismount (%flash%) devdismount (%disk%) devdismount (%disk%) devmount (%flash%) devmount (%rom%) devmount If the device is already mounted, then the following operators may change the search order: • initializedisk • devformat • setdevparams Sending these operators has the following effect on the devices in the search order: 1 If mounted, (%device%) devdismount. 2 Formats the device. 3 If dismounted in step 1, (%device%) devmount. If you do not want a device searched, unmount it and leave it unmounted. Note: Do not leave the ROM device unmounted. All internal fonts are contained on the ROM device. In the previous examples, use the devmount and devdismount operators outside the server loop. We recommend that you place the requests in a stop context so that if the devices do not exist, error recovery can take place. Changes made to the search order remain in effect.

  • 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
This occurs because the file name actually written is
iconimage.data
. When
setfilenameextend
is enabled (the
default), all PostScript emulation file operators treat file name operands as
filename.data
; when disabled, they
treat file name operands literally.
If you receive unexpected
undefinedfilename
or similar errors, try toggling
setfilenameextend
and sending
your print job again.
Device search order
If you are using the PostScript emulation operators
run, file, renamefile, status,
or
eexec
, then you do not need
to specify the device. If you omit the device name, devices are searched in the default order: hard disk, and
then flash memory. If the PostScript emulation code
(myfile) (w) file
is encountered, then the file on
the hard disk is used.
Note:
Files cannot be created in ROM.
If a device is not specified, then the operator
deletefile
searches only the first device in the default search order.
Use the PostScript emulation operators
devmount
,
devdismount
to change the order. The order the devices
are mounted determines the default search order. For example, if you want to place the disk device after the
flash memory in the default search order, then use the following command sequence:
(%disk%) devdismount
(%disk%) devmount
To change the order so the devices are searched as hard disk, flash memory, and then ROM, use the following
PostScript emulation command sequence:
(%rom%) devdismount
(%flash%) devdismount
(%disk%) devdismount
(%disk%) devmount
(%flash%) devmount
(%rom%) devmount
If the device is already mounted, then the following operators may change the search order:
•
initializedisk
•
devformat
•
<</InitializeAction>>setdevparams
Sending these operators has the following effect on the devices in the search order:
1
If mounted,
(%device%)
devdismount.
2
Formats the device.
3
If dismounted in step 1,
(%device%)
devmount.
If you do not want a device searched, unmount it and leave it unmounted.
Note:
Do not
leave the ROM device unmounted. All internal fonts are contained on the ROM device.
In the previous examples, use the
devmount
and
devdismount
operators outside the server loop. We
recommend that you place the requests in a
stop
context so that if the devices do not exist, error recovery can
take place.
Changes made to the search order remain in effect.
Flash memory and hard disk
131