Updating to Emtexgi 2.08

(32-bit version only -- latest 16-bit version is 2.071)

What files do I need?

The minimal requirement for updating emtexgi is the latest version of emtexgi.zip from here, plus unzip.exe (if you don't still have it, grab it from here).

Beyond that, you may want to get one or more of the packages for which support has been added since the release of emtexgi 2.0, if you don't already have them. These are:

If you are updating from the original 16-bit version of emtexgi (2.0 Beta) to the new 32-bit version, you will also need dll95.zip, rsxwin31.zip and rsx521b.zip, also from the getit page.

March 1997 emTeX files

Finally, you may wish to replace those emTeX files which were updated in early March 1997. These are the LaTeX2e macros, contained in l2input.zip and l2tools.zip, and the ``386'' executables, mf386.exe and tex386.exe, contained in mf4b.zip and tex4b.zip respectively. There are links to all of these files on the getit page. The automatic update routine discussed below should work for these files too.

And what do I have to do?

This depends on whether you have a "standard" installation or not. If you have a standard setup -- i.e. if you originally installed the emtexgi package using emtex.bat and you've haven't moved anything important (like program files or whole directories) since then -- you can use the program update.bat. Otherwise you'll probably have to update manually.

Automatic update: Just grab all the files you need/want, as explained above (including the updated emTeX files if you wish); put them all in a temporary directory together, on the same drive as your emtex installation; and, at the DOS prompt, run update.bat, supplying two parameters: The first should be 31 or 95 (for 16- or 32-bit Windows respectively), and the second (actually it's only required for 32-bit Windows) should be the full path to your windows system directory for 32-bit DLLs (e.g. c:\windows\system or c:\winnt351\system32). That's mostly all -- with one exception: the update to the Type 1 Computer modern fonts is separate. You need to run bluesky.bat (see below). Finally, you can delete the left-over stuff in the temporary directory.

Manual update: You should unzip emtexgi.zip in a temporary directory (either selectively or in toto) and move various files into place as follows:

If you have downloaded any of the newly supported packages, install them thus: unzip the babel, AMS and ispell files into the parent directory of the emtex tree; unzip the graphics zipfile into the emtex texinput directory. For example:

unzip babel.zip -d \
unzip amsfiles.zip -d \
unzip ispell.zip -d \
unzip graphics.zip -d \emtex\texinput

If you are installing the graphics package, then after unzipping the file as above, put the file emtgrfx.ins from emtexgi.zip (or from here) into the directory \emtex\texinput\graphics.

If you are installing the Type 1 Computer Modern fonts from Bluesky Research, put cmps-pc.zip, bluesky.bat and config.bsr in the same temporary directory, on the same drive as your emTeX installation, and run bluesky.bat at the DOS prompt. If you want these fonts installed somewhere other than under \texfonts, specify an alternative path on the command line (they will go into a subdir "ps" of whatever directory you specify).

If you are doing a manual update from 16-bit emtexgi to the 32-bit version with support for long filenames, you will need to deal with dll95.zip, rsxwin31.zip and rsx501b.zip.

If you want to update the LaTeX2e macros manually then unzip l2input.zip and l2tools.zip into the parent directory of the emtex tree. If you delete emtex/btexfmts/latex.fmt, then emtexgi will remake the LaTeX format for you, using the latest version. The new emTeX executables, mf386.exe and tex386.exe, are just drop-in replacements for the old, but if you want tex386 to handle long filenames you have to do the ``rsxopt'' thing as shown in the code fragment above.

And that's all.

What if I got "Error loading from file"?

If you have tried unsuccessfully to update to the 32-bit version of emtexgi on a previous occasion, getting this error message from Windows 95, then please accept my apologies, and visit the DLL fix page.