Black Box 4

home *** CD-ROM | disk | FTP | other *** search

/ Black Box 4 / BlackBox.cdr / os2 / dvidrv1.arj / EMTEX / DOC / ENGLISH / DVIDRV.DOC next >

Wrap

Text File | 1990-09-25 | 81.2 KB | 1,859 lines

============================================================================== DVIDRV 1.4d VERSION: 25.09.1990 ============================================================================== The dvidrv drivers output DVI files to a printer or to the screen. They will work with the following font file types: Extension ID PXL 1001 (32-bit words) PXL 1002 (8-bit words) PK 89 (packed) The font files do not have to have one of these extensions as their format is determined by their contents. PK font files with an ID of 87 can NOT be used! In addition font libraries -- a dvidrv feature -- can be used. These contain several font files saving disk space and processing time. By gathering font files into libraries the number of files in directories is reduced. Disadvantages are the size of the resulting libraries and the amount of time spent in updating fonts. For more information see the fontlib document. dvidrv includes the following drivers: dviscr screen previewer (CGA, EGA, VGA, HGC, and other adapters) dvivik screen previewer (Viking I) dvimsp create graphic file (MSP or PCX) dvihplj HP LaserJet+, HP DeskJet and Kyocera F-1010 dvidot dot-matrix printers (configurable) The following parameter files for dvidot are supplied: Param. Printers Resolution Environ. /pf* file (incomplete list) h x v DPI variable default setting ------------------------------------------------------------------------------ fx80 EPSON FX and RX series 240x216 DVIFX \emtex\pixel.fx\$rdpi fx100 EPSON FX and RX series 240x216 DVIFX \emtex\pixel.fx\$rdpi lql EPSON LQ series 180x180 DVILQL \emtex\pixel.p6l\$rdpi lqm EPSON LQ series 360x180 DVILQM \emtex\pixel.p6m\$rdpi lqh EPSON LQ series 360x360 DVILQH \emtex\pixel.p6h\$rdpi lqwl EPSON LQ series (wide) 180x180 DVILQL \emtex\pixel.p6l\$rdpi lqwm EPSON LQ series (wide) 360x180 DVILQM \emtex\pixel.p6m\$rdpi lqwh EPSON LQ series (wide) 360x360 DVILQM \emtex\pixel.p6h\$rdpi p6l NEC P6 180x180 DVIP6L \emtex\pixel.p6l\$rdpi p6m NEC P6 360x180 DVIP6M \emtex\pixel.p6m\$rdpi p6h NEC P6, Panasonic KX-P1124 360x360 DVIP6H \emtex\pixel.p6h\$rdpi p7l NEC P7 180x180 DVIP6L \emtex\pixel.p6l\$rdpi p7m NEC P7 360x180 DVIP6M \emtex\pixel.p6m\$rdpi p7h NEC P7 360x360 DVIP6H \emtex\pixel.p6h\$rdpi itoh C.ITOH 8510A 160x144 DVIITOH \emtex\pixel.ito\$rdpi aiw Apple Imagewriter 160x144 DVIAIW \emtex\pixel.aiw\$rdpi dmp130 Tandy DMP-130 240x216 DVIDMP \emtex\pixel.fx\$rdpi ibm4201 IBM Proprinter 4201 240x216 DVI4201 \emtex\pixel.fx\$rdpi ibm4202 IBM Proprinter 4202 240x216 DVI4202 \emtex\pixel.fx\$rdpi ibm4207l IBM Proprinter 4207 180x180 DVI4207L \emtex\pixel.p6l\$rdpi ibm4207m IBM Proprinter 4207 360x180 DVI4207M \emtex\pixel.p6m\$rdpi ibm4208l IBM Proprinter 4208 180x180 DVI4208L \emtex\pixel.p6l\$rdpi ibm4208m IBM Proprinter 4208 360x180 DVI4208M \emtex\pixel.p6m\$rdpi Printers of type Proprinter 4207 and 4208 must be set to AGM (see printer's manual). Not all printers of the EPSON LQ series support 360x360 DPI (lqh.dot and lqwh.dot). Parameter files for other printers can be easily constructed - see makedot.doc. If memory in real mode (DOS) is short, dviscrs.exe should be used instead of dviscr.exe -- dviscrs.exe may only be renamed if it is run under DOS 3.0 or later. This version runs in real mode, needs less memory is somewhat slower. Otherwise it behaves exactly like dviscr, for instance, the default name for the log file is `dviscr.dlg'. Running dvidrv ============== dviscr ? dvivik ? dvimsp ? dvihplj ? dvidot ? display the more common options, to get a list of all the options, type ?? instead of ? dviscr [options] input-file [options] dvivik [options] input-file [options] dvimsp [options] input-file [options] output-file [options] dvihplj [options] input-file [options] output-file [options] dvidot parameter-file [options] input-file [options] output-file [options] If arguments are omitted the program will prompt for them (cf. the // option.) dvidot is an exception: the parameter file name must always be present. More than one argument may be entered at each prompt, these arguments will be interpreted as if they had been entered on the command line. A null entry for the input file will cause the file `texput' to be used. The dvidot parameter files (the default extension is .dot) are sought in the directories listed in the PATH environment variable. The name of the file MUST be given on the command line and must be the first argument. For dvimsp the default extension for output files is `msp' (/o1 or /o2 used) or `pcx' (/op used) but the other drivers have no default. The output filename can be PRN, LPT2, COM2 if required (not for dvimsp, of course). If the output is sent to a file then the file can be printed with COPY /B file PRN The `/b' is important as otherwise the copy will terminate at the first ^Z byte encountered. Under OS/2 a hyphen can be put in place of the output file name, output will then be sent to stdout and can be piped into another program. Usually, dvimsp creates only one graphic file, containing the first selected sheet. Multiple graphic files (one for each sheet) can be created with one dvimsp run by using one or more (consecutice) `?' in the output file name. The question marks will be replaced by a number (with leading zeros): 1 for the first sheet, 2 for the second, and so on. If there's one `?', up to 9 graphic files will be created, if there are two `?', up to 99 graphic files will be created, and so on. Example: dvimsp @lj.cnf mytext page?? creates the graphic files page01.msp to (at most) page99.msp. When entering the options in response to a driver prompt the `-' or `/', which is required on the command line, need not be entered. An input filename, output filename or option can be replaced by @response-file. This will cause the lines in the response file to be read and interpreted at this point after which interpretation of the command line will continue. The response file line length may not exceed 127 characters. An example: dvidot fx80 @fx.cnf test prn First the arguments in fx.cnf will be processed, the file test.dvi will be printed with the output going to the device PRN. @response-file can be entered at a program prompt as well as on the command line though, in this case, the arguments read from the file will not be displayed on the screen. Arguments can also be passed to the program through environment variables which are scanned for first. It is recommended, however, that only options, or response files containing only options, are put into environment variables; if a file name is entered then only this file can be processed. The first environment variable looked for is DVIDRV and the next is one with the same name as the driver. dvidot uses a further environment variable with a name set in the parameter file. For example, to set /pd=c:\mydvi as a default option for dviscr, the operating system command: set dviscr=/pd=c:\mydvi can be given. Options which are common to all the drivers should appear in the DVIDRV environment variable. If, for instance, units should all be in mm then the system command set dvidrv=/umm can be entered. This will affect all the drivers. Before evaluating an argument line be it the command line, a prompted line, an environment variable or a line from a response file, all elements of the form `%name%' will be replaced by the contents of the environment variable NAME (as in batch files). If there is no environment variable with this name, the token is ignored. If the environment variable NAME also contains a token %name% then it will not be expanded but copied without change. This construction is of most use in response files: for example, to set directories with an environment variable without making changes to the response file. A single % starts a comment: all characters to the end of the line will be ignored. A `@' at the beginning of a line (column 1) causes the rest of the file to be ignored - this allows a driver log file to be used as a response file. Options ======= `#' stands for a number which will sometimes be followed by a dimension (the dimension must be in lowercase). `+' stands for `+' or `-'. + turns the option on, - turns it off. If the option is not followed by either + or -, it is turned ON. `*' stands for any other type of argument All options must be preceded by - or /. Options may be separated by spaces or another option may follow immediately: in this case the following option must start with /. There must be no space between an option and its argument: however, they can be separated by :, = or :=, for example /t10mm /t:10mm /t=10mm /t:=10mm are all acceptable forms. Options which require a file or directory name (for instance, /pf* and /pl*) can also have :, = or := between the option and its argument. Note: = may not appear in an environment variable and cannot be given as an argument to a batch file. Semicolon can also not appear as an argument to a batch file (in connection with lists of files and directories). Options for message output ========================== /? display help and default or actual values (only displays necessary options) /?? display help and default or actual values (displays all options, including those set only once) /v# verbosity /v0 only fatal error messages /v1 /v0 plus page numbers and font substitutions in batch mode /v2 /v1 plus serious warnings, `Loading ...' and the DVI file comment /v3 /v2 plus all warnings and \special's /v4 /v3 plus statistics and the names of font files /v5 /v4 plus comments in the font files the default is /v2 Note that /fl-1 suppresses font comments and warnings of absurdities in the font files. Page selection options ====================== These options select the pages to be printed. In the following the difference between "pages" and "sheets" should be noted: There may be multiple pages on one sheet (n-up printing, see below), the sheets are numbered sequentially, the pages are numbered according to the TeX page number assigned to them. The options are applied in the order they are shown below. Initially, all pages are to be printed. The first option removes certain pages from consideration, the second then restricts the remaining pages and so on. /b* Select the first sheet to be printed. The DVI file will then be read from the beginning until a matching page is encountered. Further page selection will now begin, starting at the sheet containing this page. An asterisk stands for any page number: at most 10 numbers can be given which will be compared with \count0 to \count9 -- omitted numbers will be replaced with *. The default is * which means begin at the first page in the file. Example: /b-3.*.4 selection begins with the page having \count0=-3 and \count2=4 /e* Select the last sheet. After finding a suitable first sheet, the DVI file search will continue until a page matching this option's specification is encountered. The sheet containing this page will be the last one. The sheets encompassing the range of pages selected by /b* and /e* will remain selected. The default is *: this is an exception, it means that NO matching for the last page will take place. Example: /e10.5 the last sheet is the one containing the page with the page number 10.5 /2* Double sided printing: every other sheet is selected. /2o (odd) selected sheets 1., 3., ..., /2e (even) selects the sheets 2., 4., ... The default is /2-, all sheets are selected. Example: /2o double sided printing, first part /2e double sided printing, second part /k# The number of sheets to skip: the first # of the sheets in the chosen range will be skipped. The default is 0. Example: /k1 skip one sheet /n# The number of sheets to print: at most # sheets will be printed. Default: no limit. Example: /n=10 at most 10 sheets will be printed /z+ Print the sheets in reverse order, starting with the last sheet selected. The default is /z-, print the first sheet first. /np# Print # copies of each sheet: each sheet will be printed # times before going on to the next sheet (default: 1 -- print each sheet once only). This option is not supported by dviscr, dvivik and dvimsp. /nf# Print the whole file # times (default: 1 -- print the file once only). If, with the option setting /np1/nf1 (default), sheets 1 and 2 are printed then, with the options /np2/nf3, these sheets will be printed in the following order: 1 1 2 2 1 1 2 2 1 1 2 2 This option is not supported by dviscr, dvivik and dvimsp. Font options ============ Most of these options are set only once, during installation (in a response file). /fb Batch mode. If a font is not found then it is sought first in magnification 1000, if it is still not found then cmr10 in the required magnification is sought, if this also fails then cmr10 at 1000 is sought.) It is a fatal error if this search fails and the program will terminate. This font search method can be altered with a font substitution file. If a graphic file is not found and batch mode has been selected then again the program will end. /fb is switched off by either /fc or /fi. /fc Change mode. Before a font or graphic file is loaded, the name of the file can be changed. /fc is switched off by either /fc or /fi. /fd# This sets the internal variable max_drift. If the character or line spacing is uneven, a different value can be tried: the usual values range from 0 to 3. The default value is not the same for all drivers, use /?? to find out what it is. /fi Interactive mode (default). If a font or graphic file cannot be found, the user is asked for help. /fi is switched off by either /fb or /fc. /fl# Font load limit. When the driver first loads the font parameters from a font file (`Loading font ...') all the characters are loaded which need no more than # bytes of memory. /fl-1 is a special case: the font parameters are loaded only when needed; initially, only the existence of the font file is checked. /fl-1, however, also stops warnings about absurdities in the font files and should only be used when you are sure that the fonts are alright. The default is 300, that is, all characters which need 300 or fewer bytes of memory are immediately loaded. If later a (larger) character is required which has not yet been loaded, the font file will have to be opened again. If dviscr or dvivik is used with fonts on a fixed disk, it is better to use /fl0 or /fl-1 as the first page appears on the screen more quickly (initial font load takes a little time.) If the driver complains about lack of memory, it may help (but not necessarily) to use /fl0 or /fl-1; this doesn't reduce the memory required by the driver but may improve the way the available memory is used. Example: /fl=0 no initial character loading /fl-1 load characters on demand /fl:1000 initial load of all characters smaller than 1000 bytes /fs# Font scaling. These options are used to reduce the size of the font /fsx# allowing a font generated for a higher resolution device to be used /fsy# at a lower resolution (disk space!). The reduction is accomplished by replacing the points in the rectangle of width /fsx# and height /fsy# by a single point. If the rectangle is a square, /fs# can be used to set the width and height to the same value. The values may lie in the range 1 to 8. Fonts reduced by this method appear markedly worse than fonts generated by Metafont directly. The desired resolution must be set with the /rf# option. Example: /r180/fsx2/rfx360 replace the P6L fonts with reduced P6M fonts Page layout options =================== /tr# Output transformation /tr0 normal output /tr1 rotate 90 degrees anticlockwise /tr2 rotate 180 degrees /tr3 rotate 270 degrees anticlockwise /tr4 reflect in the \ diagonal /tr5 reflect vertically /tr6 reflect in the / diagonal /tr7 reflect horizontally In practice only /tr0 and /tr1 are most often used. The transformations when applied to the pattern A B C D E F are 0 1 2 3 4 5 6 7 A B B D F F E E C A A C E E F F D B B A C D A C E D C F D B B D F C D E C A D C E F B A A B F E Important: set the page height and width correctly with /h# and /w# (for coordinate transformations) Note: the same page dimensions can be used for all transformations, that is, /h# and /w# need not be changed. The margins set with /t# and /l# are `above' or (to the) `left' (of) the text and will be transformed. The same goes for /cx# and /cy#. However, the borders set by /la# and /ta# are `printer borders' and will not be transformed. Note: if /rx# and /ry# differ then different fonts will be needed when rotating by 90 or 270 degrees or reflecting in a diagonal -- this applies to the Epson FX-80/100, NEC P6/P7 (360x180dpi) C.Itoh 8510A and Apple Imagewriter printers. Note: for key assignments for dviscr/dvivik see <K> and <T>. Current limitations for the transformations 1 to 7: -- large characters don't work -- \special{em:graph} doesn't work /h# Set the page height. This value is used by dviscr and dvivik to display the page edges as lines. dvimsp uses this value to set the size of the graphic file unless /om+ is selected. Printer drivers use this value to decide how much of the page can be printed; however, form feed is used to throw a page and so the physical page length must be set on the printer. `dvidot itoh' and `dvidot aiw' are an exception, they use the value set by /hf# for page throws. Example: /h12in set the page height to 12in /l# Left margin: the printed page will be moved # to the right. Default: 1in. Example: /l1cm set the left margin to 1cm /la# Adjust the left margin. Print adjust.dvi with the options /la0/l0 and measure the distance from the left margin to the printed square. Take an inch (25.4mm) off this and use the resulting value with /la#. This will give the exact margin requested with /l#. More exactly: with /la=x and /l=y the printed page will be moved to the right by y-x. The default value depends on the driver. /t# Top margin. The printed page will be moved down the page by #. Default: 1in. Example: /t-.5 everything moved down the page by 1/2 units (assuming /ta0; units are normally inches, cf /u*). /ta# Adjust the top margin. Print adjust.dvi and measure the distance from the top edge of the paper to the square. Take 1 inch (25.4mm) from this value and use the result with /ta#. This will then give a top margin of # with /t#. More exactly: with the options /ta=x /t=y the printed page is moved y-x down the page. The default value depends on the driver. /w# Set the page width. dviscr and dvivik use this value in displaying the edge of the page. dvimsp uses this value to determine the size of the graphic file unless /om+ is given. The dvidot driver reduces this value by 1px if the value given is exactly the maximum page width. 'dvidot fx80', for example, reduces this width by 1px if, when converted, it is exactly 1920px. Example: /w22cm set the page width to 22cm Two-up printing and changing margins ==================================== /c? Display all /cx# and /cy# values /cf# Starting value for displacement index (default: 1). The displacement index selects the pairs of /cx# and /cy# values which will be used for the current page. The index is increased by 1 for each page, when the final value is passed, the index is reset to 1. The final value is given by /cp# or is taken as the highest index set by /ci# depending on which is the greater. On the first page positions 1 and #-1 remain unused. Note: /cf# affects the page selection. Example: /ci2/cx4in /cp2/cf2 Two pages will be printed on each sheet. The first page will be printed the RIGHT half of the first sheet, the second on the LEFT half of the second sheet and the third on the RIGHT half of the second sheet, and so on. /ci# This selects the index for the following /cx# and /cy# values. There is a shift of the whole printed page (determined by /l#, /la#, /t# and /ta#) and a shift of each individual page which is printed on the same sheet. Up to 16 pages can be printed on 1 sheet of paper output and the x and y offsets of a component page are saved in one of the 16 positions selected by # (the standard values are in /cx0 and /cy0). /ci without an argument increments the current value of the index by 1. The initial value of the index is 1. The highest value of # -- or the value set by /cp#, if greater -- determines how many different page positions there are. Example: /ci2/cx4in the page in position 2 is shifted 4in to the right. /cp# This sets the number of pages to be printed on a sheet. This value can be smaller than the number of page positions but must then be a divisor (otherwise the result will be somewhat unusual). Initial value is 1. If there are 4 page positions set (with /cp2 and /cf1) then the pages will be positioned on the sheet in the following manner: Page Sheet Position 1 1 1 2 1 2 3 2 3 4 2 4 5 3 1 and so on. Here two pages are printed on each sheet with the sheets alternating between two margin settings -- with a suitable choice of page position, of course. /cx# the x and y offsets of the page in the position selected by the /cy# preceding /ci#. A complete example: /ci2 /cx4in /ci3 /cy4in /ci4 /cx4in /cy4in /cp4 Printing 4 pages on a sheet: the positions selected are: 1: /cx0in /cy0in (top left) 2: /cx4in /cy0in (top right) 3: /cx0in /cy5in (bottom left) 4: /cx4in /cy5in (bottom right) /cx-1cm /ci /cx1cm The first page will be offset 1cm to the left, the second 1cm to the right, the third 1cm to the left, and so on (one page is printed on each sheet). You are advised to create a response file for each variant which can then be put into effect by simply including @response-file in the arguments. Thus the, not exactly simple, calculation of the appropriate offsets need be done only once. Example (dviscr @twoup /o8): % twoup /ci1 /cx0 /cy0 /ci2 /cx8.5in /cy0 /cp2 /cf1 /w17in Magnification and resolution ============================ /m# the magnification in the DVI file is replaced by # which can take any value from 100 to 16000. The values are the same as those used for \mag, that is, the magnification multiplied by 1000 (/m1000 gives the normal size) or as h, 0 to 5, they represent \magstephalf, \magstep0 to \magstep5. The values 6 to 9 will be similarly interpreted. Make sure that fonts in the sizes chosen are available! Example: /m1200 magnified by 1.2 /m500 reduced to half size /mh magnification by 1.095 /m1414.213562 magnified by sqrt(2) /r# set the resolution. /rx# sets the horizontal resolution, /ry# the /rx# vertical and /r# both at once. The default value depends on the /ry# driver: dviscr /r300 dvivik /r300 dvimsp /r300 dvihplj /r300 dvidot set in the parameter file These values are in dots/inch (dpi). Make sure that the appropriate fonts are available! A number of parameters can only be calculated when the resolution is known: the driver will only convert the values when all the options have been read. Therefore the /r# option doesn't have be the first one. See also /rf#. Example: /r180 the resolution is 180dpi /rf# Set the font resolution, the argument is in dpi. This option will /rfx# usually be used together with /fs#. The horizontal and vertical /rfy# resolution can be set individually with /rfx# and /rfy#. If /rf# is omitted, the value used for the font will be that set by /r#. /rg# Set the resolution for the graphic files, the argument is in dpi. /rgx# This option merely sets the values which will be used for $r and /rgy# $s in /pg*. The horizontal and vertical resolution can be set individually with /rgx# and /rgy#. If /rg# is omitted, the value used will be that set by /r#, Directory and file name options =============================== /p@* the default directory for response files. If a response file is not found it is sought in the list of directories given by /p@*. If it is still not found, the directories listed in the PATH environment variable are searched. The default value is \emtex\texinput. Example: /p@c:\emtex\dvidrv\ /pd* the default directory for DVI files. If a DVI file is not found, it is sought in the list of directories given by /pd*. The default value is \emtex\texinput. Example: /pd=d:\dvi\;d:\mytex /pf* the default directory for font files. Font files are sought in the list of directories given by /pf*. In the directory list `$s' is replaced by the (obsolete) PXL size (resolution in dpi multiplied by 5) and `$r' by the resolution (dpi) -- note that both must be in lowercase. The default directory depends on the driver: dviscr \emtex\pixel.lj\$rdpi dvivik \emtex\pixel.lj\$rdpi dvimsp \emtex\pixel.lj\$rdpi dvihplj \emtex\pixel.lj\$rdpi dvidot set in the parameter file, cf. the table above If more than one path is given they must be separated by semicolons. The entry: /pfc:\fonts\pxl$s;c:fonts\dpi$r when used to seek the font cmr10<300> will cause the following two directories to be searched \fonts\pxl1500 \fonts\dpi300 See also the search rules for fonts. Example: /pf=c:\fonts\epson\$r /pg* the default directory for graphic files. A graphic file will first be sought in the current directory and then, if not found, in the directories given by /pg*. Here again `$s' will be replace by the magnification and `$r' by the resolution (they must be in lowercase). The name used for the search will be that given in the \special{em:graph xxx} command. If this is not found and it doesn't have an extension, the files xxx.msp and xxx.pcx will also be looked for and used if found. The default setting is \emtex\texinput. Example: /pg:=c:\win;c:\emtex\doc\gr$r /pi* printer initialization file. The file given by /pi* will be sent to the printer immediately after it has been reset. Example: /pi:unidir.p6 /pl* this gives the names of the fonts libraries to be used. Fonts are sought first in these libraries and then as single files. Font libraries can be created with fontlib; the usual extension is FLI. Directories as well as file names can be entered here, the files will be searched for in all these directories. Example: /pl=c:\fonts;hplaser;myfonts /po* this option sets the name of the output file. If the driver is called without an output file being given, this name will be used. Default: no output file. It will be given the default extension (dvimsp uses MSP or PCX, the others have no default). Example: /po:lpt1 /ps* the name of the font substitution file. The default is no substitution file. /pt* the name of the log file. The default is the name of the driver with extension DLG (for instance, dviscr.dlg). The default extension is DLG. All the output that follows the input of the files and options is written to this file. It also contains the settings of all the options for the run. The /pt option suppresses the creation of a log file. A log file can be later used as a response file to set up the same conditions again. /pv* The directories for VF files (virtual fonts). VF files will be searched for only in these directories. The default is no directory, that is, virtual font files will not be sought. If more than one directory is listed, the directories must be separated by semicolons. /pw* Write a fontlib response file. A text file containing the fontlib commands to insert the fonts used in the run into a font library will be generated. To generate this response file alone use the option /n0. Example: /pw=new.cmd fontlib call: fontlib new /k @new.cmd Miscellaneous options ===================== // prompt for options. When // is used the driver will prompt for further options, this can be useful when the options required exceed the permitted length of the command line. /u* this option sets the default dimension unit to be used when none is given. The default is inch. The following dimension units can be used (cf. TeXbook p.57) pt point (1/72.27in) pc pica (12pt) in inch (Standard) bp big point (1/72in) cm centimetre mm millimetre dd didot point (1238/1157pt) cc cicero (12dd) sp scaled point (1/65536pt) px Pixel (resolution independent) All these units must be entered in lowercase. The /u* option affects the following options. Example: /ucm dimensional units are centimetres /uMm Error! megametres are somewhat impractical Additional options for dviscr and dvivik ======================================== /- Display white on a black background. /+ Display black on a white background (default). /hx# Set the initial position. A new page will be displayed in this /hy# position and pressing the <Home> key will cause the current page to be displayed in this position. /hx0 /hy0 is the top lefthand corner of the sheet. /hx1in /hy1in is the default setting. /o# Display with gray scale. A rectangle of a x b pixels will be displayed /ox# as one point. /o# sets both a and b, /ox# sets a alone and /oy# sets b /oy# alone. An EGA (with 16 colour display) or a VGA adapter is required. If a=b=1 there is no gray scale display. a and b can take values from 1 to 8. Really slow. The implementation is optimized for /ox# values of 1, 2, 4 and 8. Setting /ox# to 5 or 7 makes the driver almost unusably slow. If /sl is set (no scaling) and gray scale is enabled with /o# but the adapter cannot do gray scales, the /o# values are used for scaling, that is, /o3 is the same as /o1/s3. Example: /ox4/oy2 /oa# Adapter setting, the possible values are: /oa0 automatic selection (default) /oa1 CGA 640x200 /oa2 EGA 640x350 or 640x200 /oa3 VGA 640x480 /oa4 HGC 720x348, not under OS/2 /oa5 GENOA SuperEGA 800x600, not under OS/2 /oa6 Paradise VGA 800x600, not under OS/2 /oa7 Video Seven VGA 800x600, not under OS/2 /oa8 Tseng Labs EVA 800x600, not under OS/2 /oa9 HP Vectra 640x400, not under OS/2 /oa10 MDS Genius (PRIMUS II) 728x1008, not under OS/2 /oa11 EGA 640x200, 16 colours /oa12 EGA 640x350, 16 colours /oa13 EGA 640x350, 16/64 colours /oa14 VGA 640x480, 16 colours /oa15 VGA 640x480, 16/64 colours /oa16 VGA 640x480, 16/262144 colours /oa17 EGA 640x350, 2 colours /oa18 VGA 640x480, 2 colours /oa19 Olivetti M24 640x400, not under OS/2 Further modes peculiar to the adapter may be used with the following extension of this option: /oa=m;w;h;ax;bx m is a number which describes the adapter and display combination: 100 EGA with monochrome display 101 EGA with 16 colour display 102 EGA with 64 colour display 103 VGA with analogue colour display w is the screen width in pixels (320 to 1024) h is the screen height in pixels (200 to 1024) The graphics mode is set by loading registers AX and BX with the arguments ax and bx before calling Int 10H. ax and bx must be given in hexadecimal. ';bx' can be omitted if BX is to be set to zero. The semicolons may be replaced with colons if desired. If (w/8)*h exceeds 65536 then h will be reduced to 65536/(w*8). You are responsible for entering the correct values, the manual for your adapter can sometimes give further help. Example: the graphics mode selected by /oa13 can be represented as /oa102:640:350:0010 and mode /oa7 is the same as /oa103:800:600:6f05:62 /oc# Set the colours to be used (only with EGA or VGA). The possible values are 0 to 15, the default is /oc2 (green). Colours can be set singly: /ocp# page border /ocr# ruler /ocs# status line /or+ Ruler enabled (default). /os+ Status line enabled (default). If the status line is disabled, there will be a beep at the beginning and end of text or numeric input. /ou* Select the dimension for the ruler and the status line (default is pt). /sx# Reduce the size of the output page, this allows more of the page to be /sy# seen on the screen. The pixels in a rectangle of width /sx# pixels /s# and height /sy# pixels will be displayed as a single pixel. /s# sets both x and y to the same value. Possible values range from 1 to 8. If fonts in suitable resolutions are available then it is better to change the resolution with /r# as reduced characters are not pretty. Even better, use gray scaling - see /o#, but only with an EGA or VGA card and a 16 (or 64) colour display. If gray scaling is not possible, then scaling can be set with /o#, too. Example: /s2 halve the resolution (x and y) /sx4/sy2 reduce the width by 1/4 and halve the height Additional options for dvimsp ============================= /- Display white on black /+ Display black on white (default) /o* Set the graphic file format: there are two different MSP file formats - Windows 1.x (/o1) and Windows 2.x (/o2, the default). PCX files can also be created (/op). Example: /op Create a PCX file /om+ Create the smallest picture possible. The borders are made small enough for the clip defined by /h# and /w# to go into the file with no waste space. The picture in any case goes up to the top, left and bottom margins. The righthand margin, however, can have a few empty columns (up to 7 or, with /ow+, up to 15). By using /l# and /t#, non-negative margins will be ignored. By using negative margins, part of the picture can be selected as objects with negative coordinates will be not be drawn. The default is /om-: the file will contain a picture of height set by /h# and width set by /w#. /ow+ The width of the picture will be rounded up to the next greater multiple of 16px (the default is /ow-). Some programs which read MSP files need this. If you're using /op (PCX file), the width will always be rounded up to the next greater multiple of 16px. Additional options for dvidot ============================= /ox+ Use XON/XOFF flow control for COM1 to COM4. Output will be sent directly to the port. If XON/XOFF protocol is to be used then the output file must be given as COM1, COM2, COM3 or COM4, /ox+ will be ignored for any other output file (for example, AUX, LPT1, mytext.prn). If /ox- is entered or the output is not to COM1 to COM4 then output will use DOS functions. This option is unnecessary under OS/2 and is not supported. When using any parameter file but itoh and aiw: /s+ Two passes per line of output. If /s+ is selected, every line will be printed twice, the first time printing dots 1, 3, 5, ... and the second time printing dots 2, 4, 6, ... The default setting (/s-) prints around twice as fast but with poorer quality as some printers (FX-80, for instance) find it difficult to fire a needle on two consecutive positions. When one of the parameter files itoh or aiw is used: /hf# Set the page length. For page throw to work properly the page length must be set. If the page length is set to 0 (0in, for example, the default) the length defined by /h# is taken as the page length. /s+ Slow mode. By selecting /s+ printing will unidirectional (itoh.dot sets also incremental print mode); the default, /s-, sets bidirectional printing (itoh.dot set also logic seek mode). Additional options for dvihplj ============================== /oc# Delete all temporary fonts after every # pages. This may help when there is not enough printer memory for holding all required fonts, but requires more time. Default is 0: don't delete fonts. Some printers not compatible enough to the LaserJet+ require /oc0. /od+ HP DeskJet. The output is for an HP DeskJet - this option must be selected to output correctly to a DeskJet. /of# Set the initial value for font ID numbers. The default is 0, acceptable values are 0 to 32736. The fonts downloaded by dvihplj to the printer will be given numbers from # to #+31. This option allows the user avoid overwriting fonts which have already been downloaded which the user does not want deleted. However, dvihplj will delete all temporary fonts. /oi+ Initialize the printer. Before any output, the printer will be initialized (default). This can be turned off with /oi-. /oj+ Job offset. Some printers can offset sheets sideways in the output tray. /oj+ will cause the output position to be switched to the alternate offset so that the results of a sequence of print jobs can be more easily be separated. /ok+ Kyocera. The output is for a Kyocera F-1010. If you want to print on the Kyocera then you must select this option. /om# Printer memory size. This sets the available memory on the printer in Kbytes: the default is 394. If this value is set to 0 then there will be no test for memory overflow. If fonts are permanently downloaded then this value must be appropriately reduced. This option will be ignored if /od+ is set. Example: /om1500 1.5 Mbytes of printer memory available /ox+ Use XON/XOFF flow control for COM1 to COM4. Output will be sent directly to the port. If XON/XOFF protocol is to be used then the output file must be given as COM1, COM2, COM3 or COM4, /ox+ will be ignored for any other output file (for example, AUX, LPT1, mytext.prn). If /ox- is entered or the output is not to COM1 to COM4 then output will use DOS functions. This option is unnecessary under OS/2 and is not supported. Specifying font size (resolution) ================================= If the driver doesn't find a font, you can enter a different font size. Font sizes are also used in font substitution files. This font size is specified in dots per inch (dpi). As there may be some decimals, there is a more convenient method of specifying magnifications: Just append a colon and the magnification step (0 to 9, or h for 0.5) to the font size. 100:3 is an abbreviation for 172.8 (100 * 1.2 ^ 3), 300:h will be converted to 328.63353. You can specify only the colon followed by the magnification step (without an explicit font size). In this case, the font resolution set with the /rf# option will be magnified. This is especially convenient in font substition files for specifying a font size independent of the device (and its resolution). Font substitution file format ============================= % Comment % % The following substitutions will be made one after the other, the original % name/size pair will be converted using the first rule, the result then % converted using the second rule, and so on. % font -> font % e.g. am* -> cm* size -> size % e.g. 305 -> 300 font size -> font size % e.g. cmr12 :0 -> cmr10 :1 % % Delete characters or replace with a block % % Once a font has been made `black' or `white', it can not be changed back. % i* -> * /w % Invisible, white fancy -> fancy /b % Invisible, black $b % `b' like `batch mode' % The following lines apply to batch mode, after every substitution the font % is sought again. * * -> * :0 % Keep the name, font size:=font resolution (/rf#) * * -> cmr10 :0 % name:=cmr10, font size:=font resolution (/rf#) Remarks 1. The following special characters can be used in font names (old -> new): ? (old): any character matches (new): ? is replaced by the corresponding ? in the old name `old' and `new' must have the same number of ?, for example, font?? -> fnt?? * (old): matches any number of characters (new): replaced with the characters matched by * in `old' * must be the last character in the name. If `new' ends with * and `old' doesn't, * will be ignored. @ (old): matches any character (new): not allowed A (constructed) example using all these characters: font substitution string: aaa?bb@cc?dd* -> x?y?z* font to be found: aaa1bb2cc3dd456 substituted name: x1y3z456 Font search rules ================= As soon as the font is found, the search algorithm terminates. Method 0: 1. The font name and size are converted according to the rules in the first part of the font substitution file - ALL rules are applied one after the other: then the font is sought under the resulting name by method 1. 2. If batch mode is active (/fb option) and the font substitution file has a second part (after `$B'), the name/size resulting from (1) above is converted using one of the rules and this name used for a search by method 1. This is done for each rule in turn. 3. If batch mode is active (/fb option) and there is no second part to the font substitution file, the following rules will be used instead following the procedure in (2) above: * * -> * x * * -> cmr10 * * * -> cmr10 x x is the horizontal resolution times 5; in transformations 1, 3, 4 and 6 it is the vertical resolution times 5. 4. If batch mode is active and the font is still not found, the driver stops with a fatal error message. 5. If the font is not found or change mode (/fc option) is active, the user is asked for another font name - see below. Method 1. 1. The font is sought in the directories set by the /pf* option (in the given sequence) using method 2. In this search `$s' and `$r' in the directory name are replaced by the size or resolution of the font. The size is calculated as: magnification * (resolution/200) * (font size/1000) rounded to the nearest integer (200 is the default size of the Stanford fonts) for example, \mag=1200, scaled 1000, resolution 300: 1200*300/200*1=1800 Method 2. 1. The file is given the extension .VF and is sought in the directories set by the /pv* option. If found, the font is a 'virtual font'. 2. The file is sought in the font library files (in the order given). 3. The file itself is sought. 4. If the file has an extension (for instance, .PK) then method 2 ends. 5. Otherwise the file name is given the extension .PK and the search is repeated. 6. If this doesn't succeed, the extension is changed to .PXL and the search repeated. In the following EXAMPLES /pfc:\fonts\$rdpi /r300 /m0 and `scaled 1000' are assumed. The search for .VF files and the search in the font libraries is not performed. `cmr10' is sought in the following sequence: c:\fonts\300dpi\cmr10 c:\fonts\300dpi\cmr10.pk c:\fonts\300dpi\cmr10.pxl `cmr10.pk' is sought in the following sequence: c:\fonts\300dpi\cmr10.pk The search for `myfonts\cmr10' is done in the following sequence (the directory is given by the user, see below): myfonts\cmr10 myfonts\cmr10.pk myfonts\cmr10.pxl c:\fonts\300dpi\cmr10 c:\fonts\300dpi\cmr10.pk c:\fonts\300dpi\cmr10.pxl `myfonts\cmr10.pxl' is searched for in this sequence: myfonts\cmr10.pxl c:\fonts\300dpi\cmr10.pxl If batch mode is active there are further searches as described above. If the search fails and batch mode is not active (/fi, default), the user is asked for help, displaying the font name and a file name of the form path\font<xxxx> where xxxx is the font size (dpi). The user should then enter one of the following items: font_size choose a new size, (new xxxx) and prompt again. Examples: 300 300 dpi :2 scaled 1440 (1.44 * /rf#) 204:h 204 dpi magnified 1.2^0.5 (= 233.47081) See `Specifying font size (resolution)' [drive:]path\ choose a new directory (file name and size remain unchanged) and search again with method 0 name choose a new file name (the directory and size remain unchanged) and search again with method 0 [drive:]path\name choose a new directory and file name (size remains unchanged) and search again with method 0 [empty line] search again using method 0 with the preceding new values + multiply the size by 1.2 and prompt again - divide the size by 1.2 and prompt again b replace all the characters in the font by a black block w make all the characters in the font invisible. A font file is still needed but the characters therein are not printed. This is useful in analyzing unusual effects. The prompt will be repeated. Keyboard functions for dviscr and dvivik ======================================== Note that it is impossible to go outside the `sheet' defined by /w# and /h#. <Ctrl>+<C> exit from the program <Q> <left arrow> move the window half the screen width to the left (for smaller movements, see <F> and <C>) <right arrow> move the window half the screen width to the right (for smaller movements, see <F> and <C>) <up arrow> move the window half the screen height upwards (for smaller movements, see <F> and <C>) <down arrow> move the window half the screen height downwards (for smaller movements, see <F> and <C>) <4> move the window to the left by the screen width <6> move the window to the right by the screen width <8> move the window upwards by the screen height <2> move the window downwards by the screen height <spacebar> <Home> move the window to the initial position (chosen with /hx# and /hy# options or <H>) <7> move the window to the top lefthand corner of the page <End> move the window to the bottom lefthand corner of the page (/hx# option or <H>) <1> move the window to the bottom lefthand corner of the page <Ctrl>+<left arrow> move the window to the left margin <Ctrl>+<right arrow> move the window to the right margin <PageUp> to the previous page <9> <PageDn> to the next page <3> <Ctrl>+<PageUp> to the first page <Ctrl>+<PageDn> to the last page reversed image toggle <D> refresh the screen image <H> make the current position the home position (see /hx#, /hy#, <Home> and <End>) <F> this reduces the window movement caused by the arrow keys; it has 6 steps <C> this increases the window movement caused by the arrow keys; it has 6 steps <G> go to one of the pages selected for display. Enter a number from 1 to the number of selected pages - this page will then be displayed. <O> return to the previously displayed page - to be used after a <G>, , <S>, <Ctrl>+<PgUP> or <Ctrl>+<PgDn> command. The driver holds up to the last 20 pages displayed. The page is displayed so that the point marked by the ruler or the middle of the page appears in the same position on the screen. display a page with a given page number, the page number must be entered. The page with this page number is first sought starting from the current page going towards the end of the file, if it isn't found then the search restarts at the beginning of the file. Page numbers can contain *, for example, 1.*.5 <R> toggle the ruler display <Ctrl>+<R> toggle the scale on the ruler <S> search for text: the search starts at the beginning of the current page (or the point at which the search last stopped). Pages are then searched starting at the current page and moving towards the end of file. If this fails then the search starts again at the beginning of the file. The search can be terminated by pressing the Esc key. If no text is entered, the text from the last search is used again. The search is case sensitive, hyphens and spaces are ignored. The text can also include accented characters. If the text contains an illegal character, for instance, \ can't appear in it, the driver beeps. The ruler is placed on the reference point of the first character of the text. <W> toggle the effect of the arrow keys - either the window or the ruler (if present) is moved. After enabling the ruler with <R>, the arrow keys move the ruler. This function affects the four arrow keys, <Ctrl>+<left arrow>, <Ctrl>+<right arrow>, <Home> and <End>. The other keys continue to move the window. The effect of <F> and <C> is also changed, altering the rate at which the ruler is moved around independently of the setting for the window movement. change the dimension unit: moves forward through the <Ctrl>+ usual list of 10, <Ctrl>+ moves backward. These dimension units are used in the status line and the ruler display. See also /ou#. <+> change the gray scale display or scaling (zoom). If possible, <-> a gray scale is used, otherwise scaling. The relation between the values set by /ox#, /oy# or /sx#, /sy# is preserved. This means that a scaling of /sx7/sy8 cannot be changed. <+> increases the size of the picture, <-> reduces it. <Alt>+<G> change the gray scale setting or scaling (zoom). <Alt>+<S> One or two digits in the range 1 to 8 can be entered; these are taken to be the new factors for the gray scale (<Alt>+<G>) or scaling (<Alt>+<S>). If only one digit is given then it is taken as both the x and y value (like /o# and /s#). If two digits are entered then these uae used as the x and y factors (like /ox# and /oy# or /sx# and /sy#). <T> dviscr/dvivik can change the transformation dynamically by following <T> by a digit from 0 to 7 and <Enter>. This is, however, not possible if /rx# and /ry# were used to set different values and you wish to switch between transformations 0, 2, 5 or 7 and 1, 3, 4 or 6. <K> this toggles the coordinates used for the arrow keys between screen coordinates and transformed coordinates (if the display is rotated (do this on your own risk)). When <K> is pressed the arrow keys are transformed, pressing it again returns to the initial state. For functions <+>, <->, <Alt>+<G>, <Alt>+<S>, and <T> the middle of the screen (or, if the ruler is displayed, the point marked by the ruler) in the same position on the screen. Rotations are also made around this point, reflections put this point on the reflection axis and the size is changed with this point at the centre. If this causes the window to fall outside the page then the window is moved as necessary so that it lies wholly within the page (if possible). Entering numbers: Numbers are displayed in the status line, if it is enabled. Errors can be corrected with the backspace key or left arrow key, Esc ends an incorrect entry, Enter accepts the number. If there no status line (see /os-) is displayed, numbers are entered blind. First a beep shows that entry may begin (an initial (optional) sign followed by digits only), backspace, left arrow, Esc and Enter have the same effect. An illegal input causes a deeper beep. After pressing Enter, a higher tone is sounded. dviscr/dvivik status line ========================= The status line displays the following information: 1. At the lefthand end the step selected by<F> and <C> is displayed. 2. To the right of this is either `R' (ruler moves), `W' (window moves) or, if there is no ruler, nothing. 3. A little bit further right if gray scaling is possible, `Gxy' appears otherwise `Sxy'. These are the values set by /ox#, /oy#, /sx# and /sy# - and altered by <+>, <->, <Alt>+<G> and <Alt>+<S>. 4. The sheet number (the first page selected is sheet 1) appears in the middle of the line together with the page number. For example, 5: 10.7 shows sheet 5 which is page number 10.7 5. To the right of this the coordinates of the top lefthand corner of the window are shown (if transformed, this is not necessarily the top lefthand corner of the screen: for example, in transformation 1 the coordinates are those of the bottom lefthand corner of the screen). The position display x=0pt y=0pt is the top lefthand corner of the sheet. If the ruler is graduated then the distance between two (short) gradations is displayed as well. The gradation is chosen to make this a readable distance. Every tenth gradation is somewhat longer than the others. 6. A `*' is displayed at the righthand end of the line while the picture is being built up or while a text search is in progress. The status line can be removed by the option /os-. \special ======== The drivers can understand the following \specials: \special{em:message xxx} The text of the message is displayed immediately and appears after the page number before the closing bracket.) \special{em:graph xxx} Insert the graphic file xxx at this place. Only the file name part of xxx is used, the directory and/or drive is discarded. The upper left corner of the graphic file gets located at the reference point of a character that were printed at this place. You can use MSP (MS Paint under Windows 1.x and 2.x) and PCX (Paintbrush) files. 4 colour CGA mode PCX files cannot be used. All non-white pixels of a PCX file are printed (assuming the standard palette). For efficiency reasons, usage of MSP files (Windows 2.x) is recommended. The width of the graphic must not exceed 32760 pixels, the height must not exceed 32766 pixels. Example (the size of the graphic is 21pt by 23pt): \begin{center} \begin{picture}(21,23) \put(0,23){\special{em:graph dvitrans.2}} \end{picture} \end{center} \special{em:point n} \special{em:line a[h|v|p],b[h|v|p][,width]} \special{em:linewidth width} \special{em:moveto} \special{em:lineto} With these commands lines can be drawn at any desired angle. A point n (1 to 32767) is defined with \special{em:point n} and gets the coordinates of the `reference point.' \special{em:point n} commands can be positioned using the LaTeX picture environment. For plain TeX, see page 389 of the TeXbook. Two such points can be joined by a line: \special{em:line a,b,width} joins the points numbered a and b with a line `width' thick -- the widht can be given in any unit acceptable to the /u* option except px. The point numbers can have `h', `v' or `p' appended showing how the end of the line should be cut. `p' causes the line to be cut perpendicular to its direction, `h' make a horizontal cut and `v' a vertical cut. `p' is used as default if no cut mode is specified. Note that a horizontal line cannot have a horizontal cut nor vertical line a vertical one! Example: \special{em:line 1,2v,4pt} Points need not be defined before the lines which refer to them. Point and line definitions are local to the current page. If a number of lines with the same width are to be drawn, \special{em:linewidth width} can be used to set the default width for all subsequent lines without a `width' argument -- \special{em:line a,b}. The initial setting of the default width is 0.4pt; any \special{em:line a,b} appearing before a `linewidth' special will have this width. To avoid errors, the required line width should be set before each line graphic. There are other commands for line drawing. \special{em:moveto} sets the current (drawing) point to the coordinates of the reference point without drawing a line: \special{em:lineto} draws a line between the current point and the reference point, the reference point then becomes the current point. A polygon can be drawn with one \special{en:moveto} and a number of subsequent \special{em:lineto} commands. The width of the line will be that set by \special{em:linewidth width}. The drivers take note of all \specials beginning with `em:'; blanks may appear between `em:' and the following keyword (`message', `graph', `point', `line' or `linewidth'). Any \specials which do not start with `em:' are silently ignored. Warnings (error numbers 1xxx) ============================= If the verbosity, see /v, is set to a lower number than that given in brackets, then that warning message will be suppressed. If the warning message is marked with [F] then the warning is suppressed when the option /fl-1 is chosen. If the warning message has a driver name in brackets then it applies only to that driver. #1, #2 stand for variable fields in the message. All warnings have the format Warning 1xxx: ... In the following only the number and the message are given. When you get the error message `[cannot open dvidrv.err]', the file dvidrv.err (which contains the warning messages) couldn't be found. You'll find the text of the warning message in this list using the warning number produced by the driver. 1000: illegal number: #1 The numeric argument #1 of an option is not valid for the option or an unacceptable size is given in response to a prompt for a font file name. 1001: illegal number or unit of measure: #1 The argument #1 of an option is an illegal number or the unit is not acceptable. 1002: parameter too long: #1 The argument #1 of an option is too long. 1003: path name too long The argument of /p@*, /pf*, /pd* oder /pg* is too long. 1004: missing path name The argument of /p@*, /pf*, /pd* oder /pg* is missing. 1005: illegal page number The argument of /b* oder /e* isn't acceptable. 1008: bad option: #1 An option is misspelled or otherwise incorrect. 1009: unknown option: #1 The option #1 does not exist. 1010: invalid unit of measure: #1 The option /u* or /ou* is given with an unacceptable or misspelt unit, #1. 1017: too many file names: '#1' There are too many arguments which do not begin with either - or / and are therefore taken to be file names. Depending on the driver, only 1 or 2 file names can be given. 1018: input file '#1' not found The DVI file cannot be found. 1019: cannot create output file '#1' The output file cannot be opened. 1020: file name too long The file name argument to /pi*, /pl*, /ps*, /pt* oder /pw* is too long. 1021: missing file name A file name must be given (this warning not yet in use). 1022: file '#1' not found The file name given as an argument to /pi*, /pl* oder /ps* does not exist. 1023: cannot nest response files A response file cannot contain calls to other response files. 1024: response file '#1' not found The @responsefile cannot be found. 1025: invalid #1 argument: #2 The argument #2 of option #1 is not valid. 1100: preamble data doesn't match postamble data: [2] pre.#1=#2, post.#1=#3 The value #1 in the preamble differs from the value in the postamble. Has somebody been meddling with this DVI file? The value given in the preamble will be used. 1200: checksum does not match [2,F] font file #1: #2 input file #3: #4 The font file #1 does not match the TFM file. 1201: wrong design size [2,F] font file #1: #2 input file #3: #4 The font file #1 does not match the TFM file. 1202: wrong magnification [2,F] font file #1: #2 input file #3: #4 The font file #1 does not match the TFM file. 1203: character #1: pixel width off by #2 [3,F] The width of the character #1 (decimal) differs from the width calculated from the TFM file by more than 1, namely by #2 (always a signed number). If #2 is positive then the pixel width is the larger, if #2 is negative then the TFM width is the larger. This warning appears usually when the font file does not match the TFM file used by TeX, in particular, when the font is loaded with the wrong magnification. 1204: '#1' is not a usable font file [3] In searching for a font file, the file #1 has been found. This file, however, does not look like a font file. After issuing the warning, the next step in the search, described above, is taken. 1205: font #1 [#2] not found No suitable file for font #1 can be found. For further explanation see "Font search rules". 1206: batch mode: font #1 replaced by #2 [1] In Batch mode (cf. /fb) font file #2 has been used for font #1 as a suitable file cannot be found. 1300: '#1' is not a usable graphics file [3] When searching for a graphic file, the file #1 has been found. This file is, however, not a valid graphic file. After this warning has been issued, the search will continue according to the rules described above. 1301: graphics file #1 (graph #2; #3 DPI) not found The graphic file #1 cannot be found -- the command is \special{em:graph #2}. 1400: undefined point: #1 The point #1 is not defined though it is used in \special{em:line}. 1401: duplicate point number: #1 The point #1 has been declared more than once in a \special{em:point #1}. 1402: bad line omitted: #1,#2 The line with the endpoints #1 and #2 cannot be drawn. 1403: missing moveto A \special{em:lineto} has appeared without a preceding \special{em:moveto} Fatal errors (2xxx) =================== All fatal errors have the format *** Fatal error 2xxx: ... In the following only the number and ... will be shown. When you get the error message `[cannot open dvidrv.err]', the file dvidrv.err (which contains the error messages) couldn't be found. You'll find the text of the error message in this list using the error number produced by the driver. 2000: out of memory There is not enough memory to run. Further information is given showing how much memory was used by what. In some cases, this error can be prevented by using /fl-1. 2001: cannot open #1 file '#2' File #2 not found 2002: cannot create file '#1' 2003: cannot write to file '#1', disk full? While writing to #1 an error was noted; a possible reason for this error is that the disk is full. 2004: invalid scale factor A font or virtual font is bad. 2005: cannot use XON/XOFF flow control XON/XOFF flow control cannot be used as the port does not exist. 2006: serial interface time-out When using the XON/XOFF flow control, 60 seconds has elapsed since an XOFF was received without an XON. 2100: DVI file corrupted (undefined font) 2101: DVI file corrupted (no font selected) 2102: DVI file corrupted (DVI file ended prematurely) 2103: DVI file corrupted (position stack overflow) 2104: DVI file corrupted (position stack underflow) 2105: DVI file corrupted (bad postamble) 2106: DVI file corrupted (postamble not found) 2107: DVI file corrupted (illegal command in postamble) 2108: DVI file corrupted (bad preamble) 2109: DVI file corrupted (unexpected set_char command) 2110: DVI file corrupted (unexpected fnt_num command) 2111: DVI file corrupted (unexpected bop command) 2112: DVI file corrupted (unexpected eop command) 2113: DVI file corrupted (unexpected rule command) 2114: DVI file corrupted (unexpected motion command) 2116: DVI file corrupted (unexpected post_post command) 2117: DVI file corrupted (unexpected pre command) 2118: DVI file corrupted (invalid command) 2119: DVI file corrupted (back pointer does not point to bop) 2120: DVI file corrupted (more pages than claimed in postamble) Bad DVI file. 2121: character number #1 out of range An attempt is being made to set a character with a code outside the acceptable range (0-255). 2131: erroneous \special{#1}: undefined keyword After `em:' there is a unknown keyword in \special argument #1. 2132: erroneous \special{#1}: bad parameter The \special declaration #1 an unacceptable parameter (for instance, \special{em:point 0}). 2200: font #1 not found in batch mode In batch mode, when a font cannot be found after all the search rules have been tried, the program terminates with this message. 2201: font file error PK01 2202: font file error PK02 2203: font file error PK03 2204: font file error PK04 Bad PK font file. 2205: font #1 too big (#2 characters) This font has too many characters. 2206: character number #1 not supported This version of the driver can only handle character codes from 0 to 255; a character with a code outside this range has been encountered. 2207: font file '#1' ended prematurely Bad font file: too short! 2208: font file '#1' disappeared The font file #1 cannot be opened although it was there initially. Perhaps the diskette has been swapped. 2209: undefined character #1 in font #2 Trying to use a chacacter which is not in the font file. 2210: character too big A character is too big. 2211: character too big for reduction A character is too big to reduce(!). 2212: character #1: invalid width The widht of a character in the font file is quite impossible. 2213: '#1' is not a font library file The file selected by the option /pl* is not a font library file. 2214: use 'fontlib /2 /b#1 #2' to convert font library The font library file #2 must be converted to the new font library format by using fontlib. You should also use the /f\emtex\fontlist option when running fontlib. The batch file fontconv.bat/cmd can be used for converting all the font libraries. 2300: graphics file #1 (#2 DPI) not found in batch mode In batch mode the run is ended with this message when the search rules have been exhausted while looking for a graphic file. 2301: graphics file '#1' ended prematurely Bad graphic file: too short! 2302: graphics image too big The picture is too wide. 2303: graphics image too big for reduction The picture is too big to reduce (!) 2400: syntax error in font substitution file l.#1 Line #1 in the font substitution file has an error. 2401: missing parameter file name [dvidot] dvidot expects the name of a parameter file as its first argument. 2402: parameter file '#1' not found [dvidot] dvidot cannot find the parameter file #1. The first argument on the command line must be the name of a parameter file. 2403: invalid parameter file (#1) [dvidot] #1 is a number showing the type of error found. 2410: invalid page dimensions ... in options /w# or /h#. 2501: printer memory overflow [dvihplj] Calculation shows that the printer's memory is now full. The text will have to be split into smaller pieces. (/oc1 may help.) 2502: too many fonts per page [dvihplj] There are more fonts required on this page than the printer can handle -- split up the text or use /oc1. 2503: too many fonts [dvihplj] There are more fonts required in the text than the printer can handle -- split up the text or use /oc1. 2511: page width exceeds #1px The width of the page set by the /w# option may not exceed (converted) #1 px. 2513: line too long While expanding %name%, a line became longer than 256 characters. 2514: cannot write to fontlib response file While writing to the file given by the /pw* option an error occurred (disk full?) 2520: graphics mode not supported [dviscr] There is no graphics adapter card or the card present is not supported by this driver. 2602: VF file corrupted (premature end of DVI commands) 2604: VF file corrupted (stack underflow) 2608: VF file corrupted (bad preamble) 2611: VF file corrupted (unexpected bop command) 2612: VF file corrupted (unexpected bop command) 2616: VF file corrupted (unexpected post_post command) 2617: VF file corrupted (unexpected pre command) 2618: VF file corrupted (invalid command) 2621: VF file corrupted (unexpected fnt_def command) 2622: VF file corrupted (unexpected post command) 2643: VF file corrupted (invalid command) Bad VF file. 2603: VF file too complex: stack overflow A virtual font can use a further virtual font which can, in its turn, use a further virtual font, (and smaller fleas ...). This error message is issued when this nesting is excessive or is in an endless loop. 2640: input stack overflow A virtual font can use a further virtual font which can, in its turn, use a further virtual font, and so on ... This error message is issued when this nesting is excessive or is in an endless loop. 2641: input stack underflow Bad VF file. 2644: character number #1 out of range A character code in a VF file is unacceptable. 2645: virtual font #1 too big (#2 characters) The virtual font #1 contains too many characters. Internal errors (3xxx) ====================== All internal errors have the format *** Internal error 3xxx or *** Internal error 3xxx: ... If an internal error occurs, please tell the author. Please make copies of all files in use (DVI, MSP, PXL, PK, FLI, VF, SUB, log files) and make a copy of the error message. Please also make a note of the arguments used. Notes ===== The drivers dvimsp and dvidot (as well as dviscr and dvivik if /o, /o#, /ox# or /oy# are used) will not print characters which have a pixel row falling above the top paper edge. As this is quite possible, especially with characters from cminch, the option /t0 should not be used -- better to use /t1px which moves everything one pin width lower. Fonts may only contain characters with codes in the range 0 to 255. The width of a character may not exceed 32760 points and the height 32766. If a character needs more than 32000 bytes of memory (say, 504x507 points) the driver slows down noticeably. If MS-DOS or PC-DOS issues a printer timeout error in the middle of printing then you should this command to remove timeout checks: mode lpt1,,p (DOS 2.x and 3.x) mode lpt1 retry=r (DOS 4.0 or later) where lpt1 is to be replaced by the correct printer port designation. The text of error messages is read from the file dvidrv.err. This file must be in a directory listed in the PATH environment variable. This file has been created to save memory, not so that the user can change the messages. Output with the /v4 option ========================== dvihplj: At the end of each page: <a+b,c,d> a is the memory used for fonts b is the memory used for this page c is the number of fonts defined so far d is the number of fonts used on this page all: At the end of the program the memory usage, for example page buffers 4 40024 This means that 4 page buffers using a total of 40024 bytes were used. This memory usage table will also be printed (without /v4) if there is not enough memory. Return codes (ERRORLEVEL) ========================= 0 No errors 1 Bad argument 2 Bad \special command 100 Not enough memory 101 Not enough memory or disk space 200 Bad DVI file 201 Bad font file or font not found 202 Bad graphic file or graphic file not found 203 Bad VF file 204 Other error 205 Internal error History ======= [...not translated...] Version 1.4b (13.08.90): ------------------------ - Bug fixed: dviscr and dviscrs (1.4a) crashed when used with a Hercules Graphics Card. Version 1.4c (20.08.90): ------------------------ - Bug fixed: dvihplj confused characters. Version 1.4d (25.09.90): ------------------------ *** New font library file format. Old font libraries have to be converted to the new format by using (for instance) fontlib /2 /b300 /f\emtex\fontlist lj_1500 lj_0 The batch file fontconv.bat/cmd converts all the font library files. See README.ENG. *** The unit of measurement for printing/reading font sizes changed to dpi. This also affects font substitution files. *** Default setting for /pf* option changed: pxl$s (e.g., pxl1500) replaced with $rdpi (e.g., 300dpi). Also changed in all dot files. - New dvidot parameter files: lqh.dot and lqwh.dot for 360 DPI on EPSON LQ-550 etc. (not supported by all printers of the EPSON LQ series). - dvidot parameter files fx80.dot and fx100.dot changed to support more printers. - The dvimsp log file could not be used as response file. - dvimsp: create multiple graphic files. - dvimsp can create PCX files. (Therefore, the name of dvimsp may change soon.) -------- End of DVIDRV.DOC -------------