install.txt Guide to installation of an emTeX system with dviwin, dvips, PFE and emtexgi (2.08), using the utility emtex.bat. Allin Cottrell, January 26, 1998 Introduction: This document tells you how to install the emtexgi "package", a setup including the major components of emTeX along with the dviwin Windows previewer, dvips for generating postscript files, PFE as an editor for TeX source files, and emtexgi as a Windows-based "control panel" for all of the foregoing. In brief outline, you (a) gather a bunch of zipfiles from various ftp sites (details below), (b) run an installation batch file which unpacks and organizes the contents of the zipfiles, while performing some customization to get the various components to cooperate well, and (c) make a few final adjustments yourself (guidance supplied). The steps in detail: 0. I recommend that you first print out a copy of this guide. 1. If you do not already have a temporary directory by the name of "temp" on the drive where you plan to install your emTeX system, create one (e.g. mkdir c:\temp, or mkdir d:\temp, at the DOS prompt). 2. To install an emTeX system for Windows 3.1 or Windows 95 as per this procedure, you first need to acquire the following files, which should be placed in the temporary directory mentioned above. Please note that links to all of the files mentioned below can be found on the Web page http://www.wfu.edu/Academic-departments/Economics/ftp/getit.htm A. emTeX files: Source -- available via ftp, from CTAN (Comprehensive TeX Archive Network) sites and mirrors. In the US you'll probably want to use ftp.cdrom.com. Use instead ftp.dante.de (Germany) or ftp.tex.ac.uk (England) if these are nearer to you. Note that the "paths" to the files below are given relative to the base directory for TeX stuff on these sites. The name of this base directory differs by site, as shown below -- ftp.cdrom.com /pub/tex/ctan ftp.dante.de /pub/tex ftp.tex.ac.uk /ctan/tex-archive Path: systems/msdos/emtex name size (bytes) ==== =========== first.zip 127810 fontcm.zip 411129 fontltx.zip 47495 l2input.zip 409888 mf4b.zip 990552 tex4b.zip 1173697 The above files are essential. In addition you may want some of the following (source as above) -- I have starred those that may be particularly useful to the "average user": name size (bytes) ==== =========== bibtex4b.zip 160090 (for bibliographies) fontams.zip 651946 (Amer. Math. Soc. fonts) fontec.zip 1031835 (fonts in alternative encoding) fontemsy.zip 7080 (special emTeX fonts) german.zip 110991 (typesetting German text) l2tools.zip 209194 (additional LaTeX tools)* makeindx.zip 83493 (for indexing) mfware.zip 227054 (for advanced work with Metafont) texcad.zip 131010 (drawing program)* texware.zip 260671 (for advanced work) Yet more components of emTeX are available, but this should be more than enough to keep you going! B. Dviwin (Windows previewer for dvi files -- essential): [Source: CTAN sites, path: dviware/dviwin] file: dviwin29.zip C. Rsx and Rsxwin (run emTeX programs under Windows -- essential): [Source: CTAN sites, path: systems/msdos/dpmigcc] files: rsx521b.zip rsxwin31.zip D. Editor for TeX source files (some editor is essential, this particular one is my recommendation): [Source: PFE homepage] For Windows 3.1 -- path: http://www.lancs.ac.uk/people/cpaap/pfe file: pfe101.zip For Windows95 -- path: http://www.lancs.ac.uk/people/cpaap/pfe file: pfe101i.zip E. Dvips files (if you want to be able to produce postscript output). Note that you will not need dvipsfnt.zip if you plan to use only the regular TeX Computer Modern fonts: [Source: CTAN, path: systems/msdos/emtex/dvips] file: dvips583.zip In addition, you may want the set of Type 1 versions of the Computer Modern fonts. [Source: CTAN, path: fonts/cm/ps-type1/bluesky] file: cmps-pc.zip F. Emtexgi files (essential, unless marked as optional): [Source: CTAN, path: systems/msdos/emtex-contrib/emtexgi] files: dll31.zip (for Windows 3.1) dll95.zip (for Windows 95 or NT) babel.zip (optional, support for multilingual LaTeX) hyphen.zip (as babel.zip) amsfiles.zip (optional, support for AMSTeX, AMSLaTeX)* ispell.zip (optional, spelling checker)+ * If you get amsfiles.zip, you'll also need fontams.zip from emTeX. See above. + If you are using ispell, *don't* run share.exe at the same time. AND [Source: http://www.wfu.edu/Academic-departments/Economics/ftp/getit.htm] files: unzip.exe emtex.bat emtexgi.zip bluesky.bat (optional, companion to cmps-pc.zip) config.bsr (optional, ditto) 3. OK, now I presume you have all of the above-mentioned files (minus, perhaps, some on the optional emTeX list,and the dvips files if you don't want to make postscript) in your temporary directory. The next step is to run emtex.bat, a DOS batch file which unpacks the various bits and pieces and installs them in the right places. Emtex.bat *requires two parameters* -- * The first states whether you are using Windows 3.1 (31) or Windows 95 (95). For Windows NT, please use "95". * The second is the full path to your windows system directory. Under Windows 3.1 and Windows 95 this is likely to be just "c:\windows\system". Under Windows NT it might be different, e.g. "c:\winnt\system32" -- we want the location where 32-bit DLLs should be installed. [Please note: emtex.bat is stored on a unix server, and it may not be read properly by DOS after downloading. To check the file, run it *without any parameters* first. If the format is OK you'll get a message asking for a parameter, if it's not OK, "Bad command or filename". In the latter case try opening emtex.bat in your DOS editor, e.g. "edit emtex.bat"; save the file without making any changes; and it should be put into DOS format.] Here are some examples of the use of emtex.bat: the following commands should be typed at the DOS prompt (i.e. in a DOS box under Windows 3.1 or Windows 95/NT) in the temporary directory mentioned above (where all the zip files are located). i) For a standard installation under Windows 3.1: emtex 31 c:\windows\system ii) For installation under Windows 95 with Windows on drive D: emtex 95 d:\windows\system iii) For an installation under Windows NT (just illustrative): emtex 95 c:\winnt351\system32 [Note on Windows 95: For some unfathomable reason, you may find that Win 95 crashes when you run emtex.bat the first time. Whenever I have seen this happen, however, if you reboot and try again it works fine. This is just a warning not to have crucial unsaved work around when you fire up emtex.bat.] 4. If you chose to download the Type 1 versions of the Computer Modern fonts, now is probably a good time to run (at the DOS prompt, in the temporary directory as above) the batch file bluesky.bat. The default is to install the fonts into \texfonts\ps. If you want the fonts to go under some other directory than \texfonts, specify this on the command line, e.g. "bluesky.bat d:\fonts". 5. Having run emtex.bat successfully, you must now edit your autoexec.bat file. An example of the sort of entries you will need is provided below. You can cut and paste this into autoexec.bat if you wish. But pay attention in case any changes are required on your system (the examples presume that everything is on drive c:). If you run Windows95 you may not have an autoexec.bat already -- in that case emtex.bat will attempt to install one, but you may have to edit it. Sample autoexec.bat lines... set path=%path%;c:\emtex\bin;c:\rsx\bin set emtexdir=c:\emtex set dvidrvfonts=c:\texfonts set maketexpk=maketexp %%n %%d %%b %%m set emx=c:\rsx\bin\rsx.exe set temp=c:\temp *Note on Windows NT*: Your procedure at this point will be a little different. Please see the webpage http://www.wfu.edu/Academic-departments/Economics/ftp/nt.html for guidance. 6. If you're using ispell in conjunction with emtexgi there is one more thing to check. Look in \rsx\bin for the file rsxwin.ini, and open it in an editor. You may have to change the drive letter specification for the settings relating to ispell.exe (Windows 95) or ispell31.exe (Windows 3.1). 7. Complete the Windows side of the installation -- Windows 3.1: Select a suitable Program Group, or create a new one. With this Program Group uppermost, choose File, New in Windows Program Manager. Choose Program Item. Browse for emtexgi.exe (you should be able to find it in \emtex\mytex). Install this item. Windows 95: Create a shortcut to emtexgi2.exe somewhere appropriate. 8. Reboot your computer so that the new autoexec.bat takes effect, and you should be ready to test-drive your emTeX system. On starting up emtexgi for the first time you will have to wait a short while, as emtexgi will have to make the required "formats" for TeX/LaTeX, and the "bases" for Metafont. In addition, if you chose to install the file l2tools.zip (packed LaTeX tools), emtexgi will offer you the option of putting these tools in place automatically. If you installed dvips you will be offered the option of changing the default for high-resolution postscript from 600 dpi to 1200 dpi (useful with Lexmark Optra printers). You should also be offered the option of customizing the drive setup for dviwin. Choose "Yes" for a first-time installation -- but DON'T say yes to this prompt more than once. (If all goes well, you will only see it once.) Once the formats and bases are built, I suggest that you try the following test procedure: i) Press the "Edit" button in emtexgi. You should get a File Open dialog box, pointing towards the \emtex\mytex directory, and one of the available files there should be simple.tex. ii) Select simple.tex, and it should open in the PFE editor. This is a trivial tex source file that we can use to check that automatic font generation is working properly. There is no need to make any changes in simple.tex for now. Minimize PFE (shrink it to an icon). iii) Back in emtexgi, press the "LaTeX" button. This should typeset simple.tex (you should see an rsxwin window briefly, in which tex386 is run on simple.tex). If you get an error message, "Path not found" or similar, at this point, please see the Troubleshooting section below. iv) Back in emtexgi again, press the "View" button. Dviwin should open, and after a moment should set about making the screen font(s) needed to display simple.tex. You should see a DOS box open, in which Metafont is invoked. After this box closes, you should be able to see the typeset text of simple.tex in dviwin. v) Minimize dviwin and return to emtexgi. Now press the "ps 300" button. You should again see an rsxwin window briefly, calling dvips to make a postscript file. vi) Next try the "ps HiRes" button for a high-resolution postscript file. You should see an rsxwin window again, but there will be a missing font. Emtexgi will then call Metafont to make the missing font. Once the font is made, the dvips job can be run again -- this time the postscript file should be made without any font being missing. Note that this distribution does not come with any pre-made fonts. They will all be made on demand. Fonts are kept to a minimum in simple.tex to illustrate this process. The first time you open a "real" tex file in dviwin you will have to wait a little while, as several additional fonts may have to be made. This is an initial "setup cost" -- once you've opened a few documents the fonts will be in place and they won't have to be re-made. [Watch for one thing. If you interrupt dviwin (press ctrl-c) while it's in the process of calling Metafont, nothing dire will happen, *but* this may reset dviwin's default action when faced with missing fonts. That is, it may turn OFF the automatic font generation. To turn this back on for subsequent sessions, in dviwin pull down the Options menu and select Missing Fonts... Make sure that the "Execute command" button is checked. Then when you exit dviwin, choose "Exit (Save Parms.)" from the File menu.] 9. Cleaning up: If the above-mentioned tests work OK, you can delete all the zipfiles in your temp directory. If you don't need documentation in both English and German you can delete one of the subdirectories under \emtex\doc. If you have no intention of working with complex virtual fonts (e.g., if you are sticking to the regular Computer Modern fonts that come with TeX) then you can also delete the directory \emtex\mytex\preview with all its contents. 10. Documentation: The manual for emtexgi is in the file emtexgi.tex, in \emtex\mytex. You can run LaTeX on this file and then view it with dviwin. Starting from a fresh installation of this system, however, you may wish to get a cup of coffee while Metafont makes the fonts to display/print the emtexgi manual; there's quite a number of them. (On a reasonably fast Pentium, however, it won't take long at all.) Besides this file, you will find several pieces of documentation for emTeX components in \emtex\doc\english and \emtex\doc\german. Several of these are referenced under emtexgi's Help menu. 11. Troubleshooting: * The most likely source of problems with emtexgi is that not all of the required environment variables are set (correctly). You can check this by opening a DOS box and typing the commands "path" and "set". With "path" you are looking for the inclusion of x:\emtex\bin and x:\rsx\bin in the DOS search path (where "x" is a placeholder for the appropriate drive letter on your system). With "set" you are looking for appropriate settings for the environment variables "emtexdir", "dvidrvfonts", "emx", "maketexpk" and "temp" -- see section 4 above. If some of these things do not show up (correctly), the first thing is to check your autoexec.bat. If everything in autoexec.bat looks OK, the next potential problem is that you are "out of environment space" (so that the settings in autoexec.bat are not actually sticking) and/or that your PATH exceeds the legal DOS length. - If your path is too long, look for some extraneous directories that can be omitted. - If you're out of environment space, put a line on the following pattern into your config.sys: SHELL=C:\DOS\COMMAND.COM /P /E:2048 Obviously, check the path to your command.com. 2048 should probably be large enough for the environment space but under some conditions you may need a bigger setting -- increase by multiples of 512. * Another potential source of trouble (relating specifically to the dviwin previewer) is wrong settings in dviwin[2].ini. Look at this .ini file (which you should find in your windows directory) in an editor. Check for the following in particular: fontpath=x:\texfonts\$r [replace "x" with the correct letter] mismethod=1 miscmd1=x:\dvidrvrs\genpk.pif /e:2048 /c x:\dvidrvrs\genpk.bat $f $m $x $y $X $Y $d $p $e [but all on one line] The last setting above is crucial for generating missing fonts. Replace "x" with the appropriate drive letter. * By default, emtexgi has rsxwin windows close immediately after program termination. This is controlled by the "-X" flag to rsxwin, which appears on several lines in emtexgi.cfg. If you temporarily delete those "-X"s, rsxwin windows will remain open, and you will be able to read any message regarding problems with program execution. Similarly, the DOS boxes that open up in some phases of the operation of emtexgi are set to close automatically. You can make them stay open (and again read any error messages). Under Windows 3.1, this is a matter of using Windows' pifedit.exe to edit the PIF files corresponding to the batch files that run in those DOS boxes. Most of the PIF files are contained in \emtex\bin. Under Windows 95, in "My Computer", click the right mouse button on the batch files (*.bat in \emtex\bin) and open their "Properties": under the "Program" tab, uncheck "Close on exit". Genpk.bat (and genpk.pif under Windows 3.1), which reside in \dvidrvrs by default, might also benefit from this treatment if dviwin's automatic font generation fails. * If something or other does not go quite right during the initial installation, it's possible that emtexgi's automatic option-storing file may get out of sync with the program. Symptom: when you try to start emtexgi, you get a message about "error 13, type mismatch". Fix: Try deleting the file emtexgirc (or emtxgirc in the 16-bit version), which should be found in the main emTeX directory (e.g. c:\emtex). Then restart emtexgi.