summaryrefslogtreecommitdiff
path: root/Master
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2006-12-26 00:35:28 +0000
committerKarl Berry <karl@freefriends.org>2006-12-26 00:35:28 +0000
commit412a3b55e9c06e9d732dbc3aab77a22b33946c88 (patch)
tree1e75d021c7a7d6a26af11ee89e428fab136d99d7 /Master
parent6f0e5de91f7cb5ea0951bc92a74a4c22722a54aa (diff)
Small Windows rewordings from Jjgod.
git-svn-id: svn://tug.org/texlive/trunk@2922 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master')
-rw-r--r--Master/texmf-doc/source/english/texlive-en/live.tex26
1 files changed, 12 insertions, 14 deletions
diff --git a/Master/texmf-doc/source/english/texlive-en/live.tex b/Master/texmf-doc/source/english/texlive-en/live.tex
index ff7cbf47f33..5079717ab72 100644
--- a/Master/texmf-doc/source/english/texlive-en/live.tex
+++ b/Master/texmf-doc/source/english/texlive-en/live.tex
@@ -1689,12 +1689,12 @@ systems of the Windows family.
Windows comes in different flavors:
\begin{itemize}
\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking,
- multithreading} environments. They are the latest\Dash and hopefully
- last\Dash metamorphosis of \acro{DOS}. This can be more or less proven
- by the fact that when booting, the PC will load the \path|command.com|
- interpreter, and if you stop the boot process at this point, you can
- ask for the current (\acro{DOS}) version and it will answer something
- like \samp{MS-DOS 7.0} (at least for the old versions of Win9x).
+ multithreading} environments, but rather updated incarnations of
+ \acro{DOS}. This can be more or less proven by the fact that when
+ booting, the PC will load the \path|command.com| interpreter, and if
+ you stop the boot process at this point, you can ask for the current
+ (\acro{DOS}) version and it will answer something like \samp{MS-DOS
+ 7.0} (at least for the old versions of Win9x).
\item Windows \acro{NT}, which is a new operating system written from
scratch, capable of true multitasking behavior, and including many
high level features.
@@ -1891,11 +1891,11 @@ equivalent of Unix hard links for executable files only under Win32.
\begin{itemize}
\item \cmdname{kpsewhich} is the tool of choice to debug any
-problem. Unfortunately, \cmdname{kpsewhich} outputs debug information
-to stderr, and the older Windows consoles do not know how to redirect stderr
-to a file. (NT and Windows 2000 consoles know how to do that. But
-the trick will work for any console.) For diagnostic purposes you can
-temporarily set an environment variable (in a \acro{DOS} box):
+problem. However, \cmdname{kpsewhich} outputs debug information to
+stderr, and the older Windows consoles do not know how to redirect
+stderr to a file. (Windows NT and later do support redirections, but
+the trick below will work for any console.) For diagnostic purposes you
+can temporarily set an environment variable (in a \acro{DOS} box):
\begin{verbatim}
SET KPATHSEA_DEBUG_OUTPUT=err.log
@@ -1905,13 +1905,11 @@ You can also set the debug level:
SET KPATHSEA_DEBUG=-1
\end{verbatim}
-If you want to redirect stderr to stdout, which is not possible
-Windows, then do:
+Similarly, to redirect stderr to stdout:
\begin{verbatim}
SET KPATHSEA_DEBUG_OUTPUT=con:
\end{verbatim}
This way you can capture both stdout and stderr in the same file.
-
\item Assuming the installation has been done in \path|c:/TeX|, check
the following values: \\
{\small