Uninstall Texlive

Each online installation of TeX Live 2019 is an utter failure. In each and every attempt I'm left with an incomplete install. With each subsequent retry the installer warns against re-installing in the default directory once files are contained there (from previous installs). Now I'm just furious and I don't want to have a trace of.

1. Uninstall Texlive
2. Uninstall Texlive Ubuntu 16.04
3. Uninstall Texlive 2020
4. Uninstall Texlive

• To install TeX Live, complete the following steps: Extract the file, and copy the TeX Live installation folder to a directory on the server. Run the following command. When the Do you want to continue with the exact same settings as before (y/N) option is displayed, enter N. Enter C to install TeX Live with the standard collections.
• I attempted to install tinytex on a GNU/Linux Trisquel distribution, but it interfered with the TeXLive distribution that was already installed so I removed tinytex via remove.packages('tinytex'). After tinytex should have been removed, I attempted to use rmarkdown for a PDF document and this is the result below.
• Uninstall texlive. To remove just texlive package itself from Ubuntu 16.04 (Xenial Xerus) execute on terminal: sudo apt-get remove texlive. Uninstall texlive and it's dependent packages. Purging texlive. More information about apt-get remove.
• To save disk space you may want to delete the old TeX live. Simply remove the folder /usr/local/texlive/2012 (my use the Terminal or in finder Go To Go To Folder ) – it contains all stuff belonging to TeX Live 2012.

** Uninstalling **

MacTeX | Donate | FAQ | Help | TUG

faq.html gettinghelp.html-->

Uninstalling TeX

There are two reasons users want to uninstall. Some casual users see TeX on the web, download it to experiment, decide that the program is not their cup of tea, and want to get rid of it. Other users have MacTeX-2020 or another earlier distribution, upgrade to the latest version, and want to reclaim space by erasing the old distribution.

The Apple Installer does not support uninstalling files. However, it is fairly easy to remove most software installed by MacTeX.

The actual TeX distribution TeX Live is by far the largest piece of MacTeX. Luckily, TeX Live is installed in a single directory on the Mac; it is not scattered over several different places. TeX Live 2021 is entirely contained in /usr/local/texlive/2021; the old TeX Live 2020 was in /usr/local/texlive/2020.

The only difficulty is that TeX Live is owned by root and lives in a location that is not commonly visible in the Finder. But it is easy to work around this problem. In the Finder's Go menu, select 'Go to Folder'; in the resulting dialog window, type '/usr/local/texlive'. You will see folders containing various copies of TeX Live. Drag the folder corresponding to the version of TeX Live you want to uninstall to the trash. You will need to provide an administrative password when asked.

The folder texmf-local is available for local additions to TeX. These local additions are used by all versions of TeX Live, so if you added files for TeX Live 2020, they are still around for TeX Live 2021. When MacTeX is installed, it doesn't touch texmf-local if it already exists, but it creates an empty directory tree if none is present.

Consequently, if you are updating TeX Live to a new version, you want to leave texmf-local alone. But if you are trying to remove all traces of TeX, then remove texmf-local by dragging it to the trash.

Uninstalling the GUI Applications

This step is easy. The GUI applications are in /Applications/TeX. To uninstall, drag them to the trash.

Uninstalling the TeX Distribution Data Structure

This data structure takes very little space, so it makes little sense to erase it. But if you must, locate /Library in the Finder and drag the subfolder TeX to the trash. You will be asked to give an Administrator password. Warning: if you have other TeX distributions, they may have also installed files in /Library/TeX, so erasing this folder is then not a good idea.

Incidentally, when you remove a TeX Distribution, say TeX Live 2020, it is not necessary to remove its related links from the TeX Distribution Data structure. The software is smart enough to know that these links no longer point to live data.

Uninstalling Ghostscript

This step is more difficult. One way to proceed is to open the MacTeX-2021 install package and select 'Show Files' from the resulting 'File' menu of Apple's installer. This will give a complete list of files installed, and their install locations. Find files related to Ghostscript and remove them.Most Ghostscript files are in /usr/local/bin or /usr/local/share.

5 Maintenance and other aspects of the TeX Live installation under Windows

5.1 What's different under Win32 from the standard Web2c?

The Win32 version of Web2c has somespecific features that need to be noticed.

Kpathsea

the hash-tables that Kpathsea builds are quite large for the TeX Live. In order to cut down the starting time of any Kpathsea-enabled program, these hash-tables have been put in shared memory. This way, when you chain the execution of several such programs, like tex calling mpost calling tex, the overhead when starting each of the programs but the first will be reduced. This change is hidden to the user, except if you set the debug flag of kpathsea to the -1 value: you will then trace access to the shared memory, which is not what you want (it is accessed very often!). What is useful in a log trace of the shared memory access is still to be defined, so the situation might evolve in the future.

kpsecheck

this command provides some option that did not fit well into kpsewhich. It will allow you to list all the files that occur multiple times across your texmf trees. This could be handy, but most of the time you will also get unwanted output (like dozens of README files)³. For this reason, you can combine the -multiple-occurences with 2 other options for including or excluding any filename that match some pattern (you can request for several patterns).

The kpsecheck command will also report the status of shared memory: in use or not used. That might be useful to know because if the status reported is 'in use', that means one or several processes are working, and the effect of any mktexlsr command will be delayed until the next time where no Kpathsea linked process will be running.

Last, this same command will report about the location it thinks Ghostscript can be found. Under Win32, for many programs, it is easier to use the Ghostscript dll, and find it by using the Ghostscript registry key than to change the PATH, which has a limited length anyway.

Web2c

the engines have a few more options than the ones from regular Web2c, and one option with a different behaviour:

• the -fmt option behaves differently. Previously and with the regular Web2c distribution, this option has 2 different meanings when you are in 'ini' or 'vir' mode. Under Win32, it has the same meaning: preload the format file specified with the argument. The meaning of building a format of such name in 'ini' mode is obtained by the new -job-name option.
• -job-name option: allows to set the name of the file resulting from the compilation process. In normal mode, it will change the base name of all files produced (.dvi, .aux, etc.), while in 'ini' mode, it will set the name of the format file written.
• -halt-on-error stop the compilation at the first error.
• -job-time set the job time to the same timestamp as the file given in argument.
• -output-directory allow to write all the output files in the specified directory.
• -time-statistics print statistics about the job run time. It is to be noted that Win9x not being a true multitasking operating system, it has no reliable timer for short periods, so the value printed is an approximation. Under NT/2K/XP, the result is quite accurate with user time and system time values allocated for this run. For Unix users: the time command is not usually available to Windows users.

5.2 Adding packages to your installation

You will find an option in the TeXLive menu (or go to Start -> Programs -> TeXLive -> Add TeXpackage menu) to run again TeXSetup.exe, but in maintenance mode this time. The steps you will go throughare almost identical to the ones the first time you run it.

The only different step is about the packages selection page. In maintenance mode, the list of installedpackages is compared to the list of packages available from your source directories. Packages that are notinstalled will be displayed in green, out of date packages will be displayed in red and up to date, installedpackages are displayed in black.

This way, you can choose to add or upgrade components, either from your CD-ROM or from the Internet,where you are likely to find some more recent version of your packages.

It is up to you to select which ones of the packages you want to install. The rest of the process is similar to thefirst installation.

If you want to add files that are not provided by the TeX Live (or fpTeX) distribution, it is recommended toput them in the $TEXMFLOCAL directory. This way, you will be safe against upgrades of the TeX Livesoftware.

The directory pointed to by $TEXMFLOCAL is initially empty. If you want to add there the supportfile for Maple (symbolic computation program) for example, you will have to put the style filesin:
c:Program FilesTeXLivetexmf-localtexlatexmaple
and the documentation files in:
c:Program FilesTeXLivetexmf-localdoclatexmaple

Next, do not forget to rebuild the ls-R databases files, either by using the right menu (Start -> Programs -> TeXLive -> Maintenance), either by manually running the mktexlsr command.

5.3 Removing TeX Live from your hard disk

The uninstall procedure is available either from the TeXLive.exe program, from the TeXLive menu or from thecontrol panel (Start menu -> Control Panel, Add/Remove Programs option). This procedure will cleanup yourhard disk of most of the TeX Live files. However, TeX is a system that is creating files and there is no mechanismto keep track of all of them. Moreover, Win32 support packages have their own uninstall procedure, which youwill have to run separately (provided you want to get rid of them). Last, the files you may havestored in $TEXMFLOCAL won't be removed. So, even if the vast majority of files are automaticallyremoved by the uninstall procedure, you will have to do some manual cleanup to actually remove all ofthem.

5.4 Running TeXSetup.exe from the command line

The TeXSetup.exe program has a number of other interesting options. You can get the list by running:

Here is the description:

--automatic-reboot

reboot without waiting user confirmation once installation is over;

--dry-run

do nothing, just log everything that will be done without this option;

--quick

use the recommended installation and default directories, ask nothing up to rebooting;

--net-method (=ie5/direct)

enable to download components with restricted licenses from the Internet (either using direct connection of Internet Explorer 5 DLLs): you need to have an available network connection and some of the packages are huge;

--remote-source-directory

this is the base url for the remote packages;

--local-source-directory

by default, TeXSetup.exe will guess the root directory of the set of files you want it to act on, if you ever upgrade TeXSetup.exe, you won't be able to copy the new version onto your CD-ROM, so you will need to use this option to specify the root of the CD-ROM;

--installation-directory

this is the root of your installation, all files will be copied under this location. The default value is c:Program FilesTeXLive;

--texmfmain-directory

--texmflocal-directory

--texmfextra-directory

--texmfhome-directory

--vartexmf-directory

--vartexfonts-directory

these are the directories used to configure the location of your files. They map directly to the texmf.cnf variables.

--with-source-files(=yes/no)

copy the source files for TeX packages, default value is no;

--with-documentation-files(=yes/no)

copy documentation files for TeX packages. Default value is yes. Beware: this is only documentation about specific packages, general documentation will be installed anyway;

--program-folder

the name of the folder under which you will find the menus;

--add-package

this is used to add or update a specific package after a first regular installation;

--scheme

install the named scheme instead of the default texlive-recommended scheme;

--maintenance

mostly the same as --add-package without specifying a package to add;

--uninstall

this option will remove anything TeX related coming from the CD-ROM, which means there can be files left if you added style files or format files, and also that supplementary tools will not be removed⁴;

--help

this option opens up a box with the list of options.

5.5 Network installation

Kpathsea knows about UNC names, so you can use them to get your TEXMF tree from the network. But thereis better than this. All the support files and configuration files, everything except the files in thebin/win32 are shareable with a teTeX or Unix TeX Live installation. That means you can use Sambaeither to mount from an NT server to a Unix workstation or the converse. Several strategies arepossible:

• Put everything on the server. Just add each set of files for the os and architecture you want to use in the bin directory. That means for example bin/win32 and bin/i386-linux. Next configure your main variables. You can use UNC names to point to the right directories under Win32.
• Install a local copy for the binaries and format files. In this case, assign $TEXMFMAIN to the main texmf tree that will be accessed remotely. Set $VARTEXMF to be a local directory which will hold local configuration files and on-the-fly generated files.

5.6 Personal Configurations

5.6.1 WinShell

Start this program from the Start menu or from the Desktop shortcut. Go to Options ->ProgramCalls.

• In the DVIWin tab, if the filename is yap, replace it with windvi.exe.
• In Ghostview tab, make sure it gives the correct path for gsview32.exe:
  C:ghostgumgsviewgsview32.exe (for 3.6, the current version)
  or
  C:gstoolsgsviewgsview32.exe (for the older version)

Click OK.

Note that the install process sets all files with the .tex extension to open with WinShell. Unless you plan touse another editor (such as WinEdt or Emacs), this is appropriate.

Unfortunately, WinShell does not have a spell-checking feature. However, if you have installed thetex-extrabin collection, your installation includes Ispell (a spell checking program found on most Unixsystems). The executable is in your PATH so ispell.exe will be found if you invoke it from a DOS window. Ifyou installed documentation, look at
C:Program FilesTeXLivetexmfdochtmlmanpagesispell.html
for information on Ispell. (Otherwise, you can find ispell.html on the CD.) If you rely on spell checking, youmay want to add an Ispell icon to WinShell. See subsection 5.9.4 of this document for how to dothat.

For an excellent commercial (but inexpensive) spelling checker, see http://www.microspell.com.

WinShell also has on-line help, which you can access via the ? on the menu bar.

Other information about using WinShell can be found in section 5.9 on p. 50.

5.6.2 Dvips

The configuration file for dvips can be found in
C:Program FilesTeXLivetexmf-vardvipsconfigconfig.ps
You may open it with any editor (WinShell will do fine) and change some parameters:

fonts

you can change the default printer METAFONTmode or printer resolution in case dvips needs to generate PK fonts. By default it is configured to use type1 versions of the CM fonts, so it should not call mktexpk too often;

printer

you can tell dvips where you want to print by default. If the ‘o' option is not followed by a printer name, then a .ps PostScript file is written. You can give dvips a printer name such as:

paper

Next, you might want to change the paper size from European (A4) to US letter by making the US letter the first paper size mentioned in the file. Scroll to the group of lines beginning with '@'. Move the appropriate lines so that this section begins with the lines:
@ letterSize 8.5in 11in
@ letter 8.5in 11in
@+ %%BeginPaperSize: Letter
@+ letter
@+ %%EndPaperSize

Note: The current TeX Live distribution has implemented (for the first time!) the procedure of makingalways up-to-date fontmaps files for Dvips and Pdftex. This is done by updmap program during installation, aswell as during any font package addition. If you add new packages by hand, edit the file updmap.cfg in$VARTEXMF/web2c.

5.6.3 Pdftex

If you want to use the program pdflatex to convert directly to pdf format, and you are usingUS letter file, edit the file
C:Program FilesTeXLivetexmf-varpdftexconfigpdftex.cfg
and change 'page_width' and 'page_height' to specify letter-size paper. These entries should read:
page_width 8.5 true in
page_height 11 true in
Save the file and exit the editor.

5.6.4 GSView

Starting from versions compatible with Ghostscript 6.50, GSView is not free anymore, butshareware. So it is not on the CD-ROM anymore.

You may want to change the papersize to US letter size. If so, open GSView from the Start menu.
From the Media menu, select Letter.

Also, there are menu settings that are supposed to give you the most readable screen image:
From Media ->Display Settings, set Text Alpha and Graphics Alpha both to 4 bits.

Note that the installation process has set all .ps and .eps files to automatically open with GSView.

For printing instructions, see section 5.8 below.

5.6.5 WinDvi

The TeXSetup.exe program takes care of associating the files with the .dvi extension with Windvi.

Open it from the Start menu (Programs -> TeXLive -> DVI Viewer). You can set it for US letter paper bygoing to View ->Options and next to Papertype, selecting US (8.5' x 11'). Click OK. Exit Windvi. You canchange other parameters from there, like the ability to execute commands included in pathspecial{}. Also, thefirst time you view any .dvi file, you may find the magnification too large. Zoom out until you get an appropriatesize.

All the configuration for Windvi is stored in the $HOME/windvi.cnf file. You can find it by running thiscommand at the prompt:

Should you have problems with Windvi, please remove the configuration file and test your problem against avanilla configuration.

5.7 Testing

You can test WinShell by opening the file sample2e.tex, found in C:LocalTeXtexmftexlatexbase.The LaTeX source should appear on the screen. Process it by clicking on the LaTeX icon on the toolbar, thenview it by clicking on the Preview (Windvi) icon.

At first, when you preview files with Windvi, it will create fonts because screen fonts were not installed. Aftera while, you will have created most of the fonts you use, and you will rarely see the font-creation window. Returnto WinShell and try dvips, then GSView.

Hint for the future: If a LaTeX run stops because LaTeX cannot find a file, you can press Ctrl-z toquit.

5.8 Printing

It is possible to print from Windvi. In this case, printing will be done using the Windows unified printer driver.By definition, it is compatible with all printers. However, there is some drawback: it can generate some hugespool files, and some (older) versions of Windows just don't like them. The advantage is that you can use featureslike embedding BMP or WMF images. You also need to make sure that the printer parameters are correctly set(subsection 5.6.5), else you will get scaled printing (printing at 600dpi on a 300dpi printer will give you only onequadrant of your page).

Printing is faster and more reliable if you run dvips to make a .ps file and then print from GSView. To printfrom GSView, first select Print... from the File menu. A Print window will appear.

If you will be using a PostScript printer, be sure to select PostScript Printer. In the newer version this is donein the 'Print Method' box at the bottom left of the Print window. You can then select any of the printers that youhave previously installed on your PC. If you fail to check the box for PostScript Printer, printing will notwork.

If you will be using your own non-PostScript printer, select Ghostscript device in the 'Print Method' box,then click on the button to the right labelled djet500 and select your printer type from the list that pops up. (In theolder version of GSView, make sure PostScript Printer is not selected, then select your printer type from the'Device' list.)

If you use WinShell and a PostScript printer, probably the most convenient way to print is to add an icon tothe WinShell toolbar that invokes dvips in a way that sends the output directly to a default printer. For detailedinstructions on how to do this, see 5.9.3 on p. 51 (More About WinShell).

5.9 More About WinShell

5.9.1 Installing Bug Fixes

WinShell's author (Ingo de Boer, thanks to him) sometimes releases beta versions of the next WinShell versionwhich are also bug fixes. You can grab them from http://www.winshell.de. Usually they are .zipfiles that only require to be unpacked in WinShell directory (c:Program FilesWinShell bydefault), either using WinZip or a similar tool, or by using unzip on the command line. If you gotsome winshellbugfix.zip file and that you saved it in the WinShell directory, then you need torun:

Say ‘yes' if you are asked if some files should be overwritten. The unzip.exe programme can be found in thesupport/gnu-utils package. If you do not have it on your machine, you can use any archiver tool like WinZipto achieve the same effect.

5.9.2 Using the Project Feature

If your document is split into several files (for example a thesis), look intoWinShell's 'Project' feature. From the Project menu, you give the project a name (e.g., Thesis), supply the nameof the main (or root) file, and then 'add' other files. These filenames display on the left of the screen where youcan double click the names to view and switch between them. Clicking the LaTeX icon always processes themain file.

Note the icons on the toolbar for toggling the project space (on the left) and the log space (at the bottom). If youare not using the Project feature, you may want to toggle off the space on the left, using the full screen width todisplay your file.

5.9.3 Printing from WinShell to a PostScript Printer

The Dvips icon on the WinShell toolbar puts the PostScript output in a file, which you can then view withGSView and print from there if you choose. However, it's convenient to add a WinShell 'program call' to dvipswhich sends the output directly to a designated PostScript printer. The steps below show how to dothis for the printer vclw; you should substitute the name of your most frequently-used printer forvclw.

1. Make the program aware of the printer:
   • Open WinShell, go to Options ->Program Calls ->User defined.
   • Click on Tool 1 in the list on the right and fill in the fields to the left as follows:

     Name: Print
     exe file: dvips
     cmd-line: -D600 %m -o vclw
     Uncheck the box for 'DVIPS first'

   • Click OK
2. Add Print to the toolbar:
   • Go to Options ->View ->Customize.
   • In the Category box, select User-Programs.
   • Select Print and drag it to the toolbar, placing it just to the right of the GSView icon.
   • You then have a choice of 'Image only', 'Text only', or 'Image and Text'. The easiest is to select 'Text only' and click OK. You should then see Print on the toolbar. (If you prefer, you can select 'Image only', then 'Edit', and edit the displayed picture to your satisfaction.)

Uninstall Texlive

Now, to print a LaTeX document, just click on the Print icon to send to your selected printer. To use a differentprinter, you will need to click on the Dvips icon to print to a file. Then click on the GSView icon and use GSViewto send to any printer you have installed on your PC.

5.9.4 Adding Ispell to WinShell

1. Add Ispell to User Tools:
   • Open WinShell, go to Options ->Program Calls ->User defined.
   • In the list on the right, click on Tool 1 (or Tool 2 if you have already used Tool 1) and fill in the fields to the left as follows:

     Name: Ispell
     exe file: ispell
     cmd-line: -t -d american %c.tex
     Uncheck the boxes for 'LaTeX first' and 'DVIPS first'

   • Click OK
2. Add Ispell to the toolbar:
   • Go to Options ->View ->Customize.
   • In the Category box, select User-Programs.
   • Select Ispell and drag it to the toolbar, placing it just to the right of the GSView icon (or the last icon you added).
   • You then have a choice of 'Image only', 'Text only', or 'Image and Text'. The easiest is to select 'Text only' and click OK. You should then see Ispell on the toolbar. (If you prefer, you can select 'Image only', then 'Edit', and edit the displayed picture to your satisfaction.)

Now, when you have a LaTeX document open, you can click on Ispell to perform spell checking.Ispell will open another window and display the first misspelled word on the left with the filenameon the right. Below that you will see the context in which the misspelling appears; often severalsuggestions for replacements are also displayed. To replace the word, enter the number corresponding tothe desired replacement. Other possible responses are listed below; for example, you can press thespace bar to ignore the misspelled word. For more information on Ispell, read the manual page:C:Program FilesTeXLivetexmfdochtmlmanpagesispell.html.

Note that when you replace a word, you will not see the correction in your WinShell windowuntil you close the file (click the X in the upper right corner) and then open it again (use the Filemenu).

5.10 Tips and tricks about the Win32 platform

5.10.1 Different flavors of Win32

What we call Win32 is not an operating system by itself. It is a set of functions – and a largeone⁵ –that you can use to write programs for different operating systems of the Windows family.

Windows comes in different flavors:

• Win95, Win98 and WinME, which are not true multitasking, multithreading environments. They are the latest – and hopefully last – metamorphosis of DOS. This can be more or less proven by the fact that when booting, the PC will load the command.com interpreter, and if you stop the boot process at this point, you can ask for the current (DOS) version and it will answer something like 'MS-DOS 7.0' (at least for the old versions of Win9x);
• Windows NT, which is a new operating system written from scratch, capable of true multitasking behaviour, and loaded with high level features;
• Windows 2K, written on an NT basis, with all the bells and whistles of Win98.
• Windows XP, which comes with Personal and Pro flavors. This is the last step in merging both lines of products (Win9x based and NT based). XP is written on an NT basis.

Win9x are able to run 32 bits programs and 16 bits programs concurrently. But the operating system byitself is not entirely written in 32 bits mode, and does not support memory protection: 16bits applications canoverwrite parts of the operating system memory! Some parts of the system like the GDI (Graphical DeviceInterface) manage limited resources like bitmaps, fonts, pens and so on for the set of all programs that runconcurrently. All the bitmaps headers available at the same time can't amount for more than 64kb. This explainsthe performance tool and the fact that you can put your system on his knees by making intensive use of graphicobjects for example.

NT, 2K and XP do not suffer from these limitations, and neither from other Win9x limitations. They are truemultitasking environments, with protected memory. They are much more responsive than Win9x because ofbetter memory management, better file system and so on.

5.10.2 Command line prompt

You will wonder: 'why would I need to use a command line prompt when I have Windows?'.

Good question. The problem is of very general nature. Not all operations can be done easilyusing only a GUI. Command line gives you programming power – assuming a clever commandinterpreter.

But the problem here is more fundamental: TeX is a batch tool. Not an interactive one. TeX needs to computethe best layout for each page, resolve cross-references and so on. This can be done only by a global processing ofthe document. It is not (yet) a task that can be done interactively.

This means that you should use TeX from a command line. In fact the situation is not so bad. There is anadvantage to write command line tools for complex processing: they are better debugged, because not tied to GUIproblems, and GUI tools can be designed to interface the command line tools. This is the case for TeXwhere you will interact with it most of the time through a GUI text editor – see section 5.6.1 forexample.

However, you may need to use the command line prompt in a number of situations, by example in case ofproblems and you want to debug your setup – see section 5.11.

Win9x

You will open a command line prompt by looking either for the MS-DOS icon in the 'Start->Programs' menu, either by choosing 'Start->Run' menu and typing in command.com

NT, 2K, XP

You will open a command line prompt by looking for the 'Command Prompt' in the 'Start->Accessories' menu⁶. You can also choose the 'Start->Run' menu and type in cmd.exe, which is the name of the brand new command interpreter for NT⁷.

5.10.3 Path separators

The Win32 API understands both / and characters as PATH separators. But the command interpreters do not!So whenever a path name is used programmatically, you can use both separators, and even mix them up in thesame path name. But on the command line, you must type as path separator. The reason is compatibility: thecommand processor used the / to introduce arguments to commands.

All this to say: do not be surprised to read path names written using the Unix convention; fpTeX is a port ofWeb2c, and aims to be compatible across platforms. For this reason, all the configuration files that need tospecify path names use the Unix convention.

5.10.4 File systems

The worse feature of Win9x with regard to TeX is probably the so-called FAT file system. TeX uses many manysmall files, with size around 1kb – 3kb. The FAT file system is old, and predates by far the multi-gigabytes harddisks we have today. It means it can't manage efficiently the 30000 TeX files found on the CD-ROM. The FATfile system will allocate a minimum of 32kb for any file on a huge partition. It means that TeX will use muchmore disk space than it actually needs.

The other, more modern, file systems available – namely FAT32 and NTFS – do not have this drawback. They manageclusters of 4kb only⁸.

5.10.5 How to add some directory to your PATH

There are pairs of variables and values which behave much like global variables inside your programs. The set ofthose variables is called the environment. Each program is initialized with a copy of the environment when it isrun. It can request and change the value of any variable. The changes happen in the copy of the environment, andis not at all propagated to the other running programs.

Your PATH is a special environment variable used to search for programs you want to run. There is a differentprocedure to change it for Win9x, WinME and NT/2K/XP:

Windows 95/98

Edit your autoexec.bat. In this file should be a line starting with PATH= and followed by a list of directories separated by ;. Please add the directory with the executables in this line. After this, this line could look as follows:

Windows ME

You need to run the special program c:windowssystemmsconfig.exe to be able to change any environment variable. From this program, select the ‘Environment' tab, and then add or modify the variable you want. You will be asked to reboot the machine upon any change.

Windows NT/2K/XP

Click left on Start > Settings > Control Panel. Now the window with the control panel icons opens. Double click on System. The System Properties window opens. Click on the tab

Uninstall Texlive Ubuntu 16.04

Environment or look for a button named ‘Environment Variables' among the dialog boxes. Now you can change the environment variables for your user account. Note: There are also displayed the environment settings for the system. Normally, you can't change the system variables unless you have administrator rights on your machine. If you want to change the PATH for all users, you will have to contact your system administrator or be the system administrator yourself–in the later case you should know what you are doing.

If there is already a PATH setting for your user account, left click on PATH. In the field Variable appears PATH while the field Value shows the current setting of PATH as a list of directories separated by ;. Add the directory where the executables are located (e.g. c:Program FilesTeXLivebinwin32). If there isn't a PATH variable for your user account, simply click in the field Variable and type in PATH, click in the field Value and type in the directory with the executables. Important: Click on the Apply button before clicking Ok, otherwise the changes to PATH won't apply to your system. Be careful when changing the environment settings.

The best way to be sure that a variable has been properly set is to open a console and type:

which should return the corresponding value.

5.10.6 TeX engines

If you have a look at the Web2c documentation, you will read that all the various TeX derived programs use thesame base engine. For example, tex.exe and latex.exe are exact copies of the same program, but each onewill use a different format file, based on its calling name.

Uninstall Texlive 2020

Under Unix, this feature is implemented through symbolic links. It saves up a bit of disk space, because someengines are used with many different format files.

The Win32 API does not know about file links. So to save up almost the same amount of memory, all the TeXbase engines have been put in DLLs (Dynamic Linked Library). This means that you will have the followinglayout:

and the latex.exe file is nothing but a rough copy of tex.exe using the same core tex.dll. The sametrick has been used for the mktex*.exe family of programs which are linked to the mktex.dlllibrary.

In fact, a generic tool called lnexe.exe is provided to build the equivalent of Unix hard links for executablefiles only under Win32.

5.11 In case of problems

Uninstall Texlive

5.11.1 What to do if latex does not find your files?

• kpsewhich is the tool of choice to debug any problem. Unfortunately, kpsewhich outputs debug information to stderr, and the Windows console does not know how to redirect stderr to a file⁹. For diagnostic purposes you can temporarily set an environment variable (in DOS box):

  You can also set the debug level:

  
  SET KPATHSEA_DEBUG=-1

  If you want to redirect stderr to stdout, which is not possible under either W9x or NT/2K/XP, then just do:

  This way you can capture both stdout and stderr in the same file.

• Assuming the installation has been done in c:/Program Files/TeXLive, check the following values:
  

  kpsewhich -expand-path $SELFAUTOPARENT	c:/Program Files/TeXLive
  kpsewhich -expand-path $TEXMF	c:/Program Files/TeXLive/texmf
  kpsewhich -expand-path $TEXMFCNF	.;c:/Program Files/TeXLive/texmf/web2c;
  c:/Program Files/TeXLive/bin/win32;
  c:/Program Files/TeXLive/bin;
  c:/Program Files/TeXLive
  kpsewhich -expand-var $TEXINPUTS	.;c:/Program Files/TeXLive/texmf/tex//

• If you have other TeX-related values already set in your environment, please, remove them. They are overriding the ones in texmf.cnf.
• Check the values from:
  

  kpsewhich cmr10.tfm	c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm
  kpsewhich latex.fmt	c:/Program Files/TeXLive/texmf/web2c/latex.fmt

• At this point, if everything is correct, tex.exe and co. should work. If it is not the case, you will need to play with the -debug=n option from kpsewhich, and check back all the values. Try to identify and report the problem.

5.11.2 What to do if your setup still does not work as expected?

There are several questions to ask about:

1. Is tex.exe on my PATH?
2. Is the TEXMFCNF variable correctly set to c:/Program Files/TeXLive/texmf-var/web2c (default value)?
3. Are there any errors in the log file generated by the TeXSetup.exe program? Errors are flagged with the sequence Error.
4. One can also go to http://www.tug.org/tex-live.html and check for any bug fix.
5. The Windows distribution on the CD-ROM is no more no less than the fpTeX distribution, so you can also go to the Web pages at http://www.fptex.org, or consider subscribing to the fpTeX mailing-list by consulting http://www.tug.org/mailman/listinfo/fptex .

The TeX Live software is complex and made of more than 250 programs and around 40000 files from varioussources. It is quite difficult to predict all possible causes for problems. Nevertheless, we will do our best to helpyou in every case.

5.12 Compiling the source files

You have the whole set of source files, comprised for Windows in the source/source.tar.bz2 archiveavailable on the CD-ROM. To be able to compile the whole distribution for Windows, you willneed:

• Windows 2K/XP
• Microsoft Visual Studio .Net
• a set of Unix tools (sed, grep, gawk, etc.) and also Perl, Flex and Bison,
• to adjust the paths in the win32/make/common.mak file according to your installation
• adjust the paths in the Perl script file win32/perl/build.pl,
• run the compilation from the win32/ directory using this command:
  
  c:texlivesourcewin32>perl ./perl/build.pl --install --log=install.log

There is a lot of work to do to make this process easier and cleaner.

5.13 Where to get more information?

The Win32 TeX distribution on the CD-ROM is also known as fpTeX. Only the packaging differs, but fpTeX isno more no less than the current TeX Live release for Windows.

The fpTeX home on the Web is at:
http://www.fptex.org/

The current fpTeX release is available from any CTAN site in the directory :
ftp://ctan.tug.org/tex-archive/systems/win32/fptex/.

The main ftp site for fpTeX is ftp://ftp.dante.de/pub/fptex/ from where beta versions of fpTeX andadditionnal tools are available. This main site is (partially) mirrored daily by the CTAN backbones in theirsystems/win32/fptex directory.

The TeX Users Group is kindly hosting a mailing-list dedicated to fpTeX. This is a very low volume one. It isused for announcements, bugs reports or as well to discuss about improvements or various users problems. Tosubscribe, read the page at http://www.tug.org/mailman/listinfo/fptex. The mailing list address isfptex@tug.org.