\begin{htmlonly}
\documentclass[dvips,a4paper]{article}
\usepackage{html,htmllist,makeidx}
\input{manhtml.tex}
%
\input{problems.ptr}		% Input counters and section
\end{htmlonly}
\internal{}%
\startdocument
%
%\section{Known Problems\label{sec:prb}\index{problems|(}}%
\tableofchildlinks*\htmlrule\index{bugs}\html{\\}%
\noindent
Here are some of the problems that were known to exist
with previous versions of \latextohtml. 
Most of those that were real errors are either fixed completely
in the current version (\textsc{v97.1}), or are much less likely to occur
within correct \LaTeX{} source. (Some are not really errors but
indications of poor style in the user's choices among
various ways to organise their source code.)\html{\\} 
Several are indeed limitations inherent in the way 
\latextohtml{} currently performs its processing.
%
\begin{htmllist}
\htmlitemmark{PurpleBall}
\item [Correctness and Efficiency:\index{efficiency} ]
The translator cannot be guaranteed to perform as expected.
Several aspects of the implementation need
optimisation and improvement. Apart from possible bugs the translator 
may place heavy demands on your resources.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\textit
%end{latexonly}
{The current version works much more efficiently than previous
versions; many subtle bugs have been identified and eliminated.}
\end{changebar}

\item [Unrecognised Commands and Environments:\index{unrecognised commands} ]
Unrecognised commands are ignored and any arguments are left in the text. 
Unrecognised environments are passed to \LaTeX{}  and the result is
included in the document as one or more inlined images.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{There are very few standard \LaTeX{} commands that are not recognised.
Many common \TeX{} commands are recognised also,
even though not explicitly mentioned 
in the \LaTeX{} \hypercite{blue book}{blue book}{}{lamp:latex}.
Any aberrant commands should be reported to the \latextohtml{}
\hyperref{mailing list}{mailing list, see Section~}{}{support}.}
\end{changebar}


\item [Cross-references:\index{cross-references} ]
References in environments that are passed to \LaTeX{}  for processing
(e.g. a \Lc{cite}, or a \Lc{ref} command), 
are not processed correctly.
\Lc{label} commands are handled correctly.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{All citation, reference and label commands should work correctly now.
Report any problems to the \latextohtml{}
\hyperref{mailing list}{mailing list, see Section~}{}{support}.}
\end{changebar}

\item[Order-Sensitive Commands: ]
Commands which affect global parameters during the translation,
and are sensitive to the order in which they are processed may
not be handled correctly. In particular, counter manipulation
(e.g. \Lc{newcounter}, \Lc{setcounter}, \Lc{stepcounter}, etc.) 
commands may cause problems.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{Counter commands now work correctly; dependencies
are also implemented.}
\end{changebar}

\index{index}
\item [Index: ]
The translator generates its own index by saving the arguments  of 
the \Lc{index} command. The contents of the \env{theindex}
environment are ignored.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{This remains true. When using the \env{makeidx} package,
very sophisticated Indexes can be built automatically.
The Index for this manual is a good example.}
\end{changebar}

\item[New Definitions:\index{extensions!definitions} ]
New definitions (\Lc{newcommand}, \Lc{newenvironment}, 
\Lc{newtheorem} and \Lc{def}),
will not work as expected if they are defined more than once.
Only the last definition will be used throughout the document.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{This remains true. Stylistically it is bad to declare new
environments or theorems outside of the document preamble,
so these should cause no problems anyway.\html{\\}
Changes to commands using \Lc{def} or \Lc{renewcommand}
should usually be made only locally, within special environments,
to set a needed parameter; 
e.g. a basic length in a \env{picture} environment.
But when such environments force an image to be generated,
then \LaTeX{} will make the correct redefinition.}
\end{changebar}

\item [Scope of declarations and environments: ]
If the scope of a declaration or environment crosses section
boundaries, then the output may not be as expected, because each
section is processed independently.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{This is inherent to the way \latextohtml{} does its processing. 
It will not be fixed until later versions change this strategy;
e.g. when \latextohtmlNG\ becomes fully integrated.}
\end{changebar}

\item [Math-mode font-size changes: ]  Math-mode font changes
made outside the math-mode are not honoured.  Thus the two equations
in \verb|$a_b$| and \verb|{\LARGE $a_b$}|
would come out looking the same.  The trick is to write
\verb|$a_b| and \verb|$\mbox{\LARGE $a_b$}$|.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}
{This remains. The work-around is effective.}
\end{changebar}
\end{htmllist}



\subsection{Troubleshooting}%
%\section{Troubleshooting}%
\index{debugging}\index{problems}\index{fixes}%
Here are some curable symptoms:

\begin{htmllist}
\htmlitemmark{BlueBall}
\item [Cannot run any of the \Perl{} programs: ]
If your \Perl{} installation is such that \Perl{} programs are not allowed 
to run as shell scripts you may be unable to run  
\fn{latex2html}, \fn{texexpand}, \fn{pstoimg} and  \fn{install-test}. 
In this case change the first line in each of these
programs from
%begin{latexonly}
\begin{small}
%end{latexonly}
\begin{verbatim}
#!/usr/local/bin/perl
\end{verbatim}
%begin{latexonly}
\end{small}%
%end{latexonly}
to
%begin{latexonly}
\begin{small}%
%end{latexonly}
\begin{verbatim}
: # *-*-perl-*-*
    eval 'exec perl -S  $0 "$@"'
    if $running_under_some_shell; 
\end{verbatim}
%begin{latexonly}
\end{small}
%end{latexonly}

\item [The \fn{install-test} script gives uninformative error messages: ]
If, for any reason, you have trouble running \fn{install-test},
do not despair. Most of what it does is to do with checking
your installation rather than actually installing anything.
To do a \textit{manual installation} just change the variable
\fn{\$LATEX2HTMLDIR} in the beginning of the file \fn{latex2html}
to point to the directory where the \latextohtml{} files can be found.

Also, make sure that the files
\fn{pstoimg}, \fn{texexpand} and \fn{latex2html} are executable;
if necessary use the Unix \fn{chmod} command to make them 
executable.

\item [It just stops. ] Check the style
files that you are using. It is possible that you are using
a style file which contains raw \TeX{} commands. In such a case
start \latextohtml{} with the option 
\Cs{dont\_include \Meta{style-file name}}. 
Alternatively, add the name of the style to the variable 
\fn{\$DONT\_INCLUDE} in your
\fn{\$HOME/.latex2html-init} file. If you don't have such a file then
create one and add the lines:
\begin{quote}
%begin{latexonly}
\begin{small}
%end{latexonly}
\verb|$DONT_INCLUDE = "$DONT_INCLUDE" . ":|\Meta{style file name}\verb|";|\\
\verb|1; 	# This must be the last line|
%begin{latexonly}
\end{small}
%end{latexonly}
\end{quote}

Another reason why \latextohtml{} might stop is that the \LaTeX{} source
file itself contains raw \TeX{} commands. In this case you may 
put such commands inside a \env{latexonly}
\hyperref{environment}{environment (see Section }{)}{sec:latexonly}.

\cbversion{97.1}\begin{changebar}
The \fn{\$VERBOSITY} \htmlref{variable}{verbosity} can be used 
to create tracing messages, which may help to locate which command 
or environment was being processed when everything stopped.
\end{changebar}

\index{unending loop}\index{looping endlessly}
\cbversion{97.1}\begin{changebar}
\item [It appears to be doing nothing.\label{looping}]
Perhaps the processor has fallen into an unending loop.
Usually there will be a bad definition, or other faulty source code,
which has caused this.
The \fn{\$VERBOSITY} \hyperref[page]{variable}{variable (see page~}{)}{verbositylevel}%
can be set to generate tracing messages, which may help to locate which command 
or environment is being processed repeatedly.
Try setting a value of `\texttt{3}'; e.g. using the commandline switch \Cs{verbosity 3}.
This will print command and environment names, as thaey are processed.
It should soon become apparent where any such looping occurs.

\item [It just fills the endlessly with dots.]
No `perhaps' here; the processor has definitely fallen into an unending loop.
See the previous item for how to detect which command or environment
is causing the problem.
\end{changebar}

\item [\Perl{} cannot parse the \fn{latex2html} script: ]
Update your \Perl{} to patch level 36. You can check which version of
\Perl{} you are using by invoking \Perl{} with the \Cs{v} option.
Earlier versions of \Perl{} than that shown above
have caused problems due to tighter control over syntax.

\item [It crashes (dumps core) as soon as it starts \label{perl}: ]
Update your \Perl{ 4} to patch level 36 or later (\Perl{ 5}).

You can check which version of
\Perl{} you are using by invoking \Perl{} with the \Cs{v} option.
\html{\\}
While you wait for your technical support people to upgrade \Perl{}
you could try invoking \Perl{} from within \latextohtml{} with 
the \Cs{d} (debug) option. Then when \latextohtml{} starts, it will
immediately fall into the \Perl{} debugger. To continue just press 
`\texttt{c<CR>}'. (This option is available only if the 
local version of \Perl{} was specially compiled to allow it.)


\item [\fn{dvips} complains about incorrect arguments:\label{dvips} ]
Please use a version which supports the command-line options \Cs{M}, \Cs{S},
\Cs{o} and \Cs{i}. ``Recent'' versions, at least after 5.516, do support them.


\item [It gives an ``\texttt{Out of memory}'' message and dies: ] 
If you are using version \latextohtml{} 0.7 or later try splitting your 
source file into more than one file, using the \LaTeX{} 
commands \Lc{input} or \Lc{include}. 
Also, try using the \Cs{no\_images} option.

\cbversion{97.1}\begin{changebar}
Perhaps the processor has fallen into an infinite loop.
Usually there will be a bad definition, or other faulty source code,
which has caused this. 
See an \htmlref{earlier problem}{looping} for
how to set the \fn{\$VERBOSITY} \htmlref{variable}{verbosity} to 
help locate the bad code leading to this memory exhaustion.
\end{changebar}%

As a last resort you may consider increasing the virtual memory
(swap space) of your machine. As an indication 
of what you might be able to do on your machine,
a very long book (about 1000 printed pages) required about 
24MB of RAM and over 150MB of swap space to convert on a local Sun Sparc ELC
running SunOS 4.1.3.
\cbversion{97.1}\begin{changebar}
%begin{latexonly}
\newline\textit
%end{latexonly}%
{Much of this memory would have been consumed during image-generation.
This part of the processing is much more efficient in \textsc{v97.1}\,.}
\end{changebar}%


\item [It gives ``dbm'' related error messages: ]
\latextohtml{} 0.7 and later requires the
Unix DataBase Management system (\appl{DBM} or \appl{NDBM}) in order to run.
This is usually part of each Unix operating system but if you 
don't have it then you may need to get it. 
\htmladdnormallinkfoot{Use \appl{Archie}}{http://www.pvv.unit.no/archie/} 
to find one.

\cbversion{97.1}\begin{changebar}
This can happen when an image is being created from a large piece
of \LaTeX{} source code. The image-reuse mechanism uses the code itself
to construct a database key. If too long, the key is invalid and may
crash \appl{DBM} or \appl{NDBM}. (In fact this error should no longer
occur in \textsc{v97.1}\,, so please advise the \latextohtml{} developers if
you get error messages of this kind.)\html{\\}
The message should contain the name of environment which caused the problem,
along with an identifying number; e.g. \texttt{eqnarray268}.
To find which exact piece of code this represents, run \latextohtml{}
again, using the \Cs{debug} switch. Then look at the files
in the working directory named \fn{TMP-part1}, \texttt{TMP-part2}, etc.
Use the unix \fn{grep} command: \texttt{ grep 268 }\Meta{dir}\texttt{/TMP-* }
to find that number in these files. 
This should enable you to locate exactly where the problem occurs.

One solution may be to wrap the whole environment within
\Lc{begin\char123makeimage\char125} and \Lc{end\char123makeimage\char125}.
This will still cause the image to be created, 
but uses just the environment name and number as the database key.
\end{changebar}%



\item [The \Lc{verb"ABC"} command doesn't work: ]
This is a nasty bug. Please use any character other than quotes; 
e.g. \Lc{verb+ABC+}.

\item [Cannot get the ``tilde'' (\~{}) to show: \hfill]
The trick here is to use the command \verb|\~{}|.\html{\\} 
Alternatively try using something like:
\url{\htmladdnormallink{mylink}{http://host/\%7Eme/path/file.html}}. 

\textbf{Warning:} Some browsers may not be able to interpret the \verb|%7E|
as a ``tilde'' character.

\item [Macro definitions don't work correctly: ]
As mentioned in other places, not all plain \TeX{} \Lc{def}-initions 
can be converted.
But you may also have problems even when using \LaTeX{} definitions
(with \Lc{newcommand} and \Lc{newenvironment}) if such definitions
make use of sectioning or \Lc{verbatim} commands. These are 
handled in a special way by \latextohtml{} and cannot be used in
macro definitions. 

In general the macro handling mechanism is inefficient and very
fragile. Avoid using macros if possible.
\cbversion{97.1}\begin{changebar}%
A greater range of macros definitions can now be handled,
especially if appropriate declarations are added to an initialization file.
\end{changebar}%


\item [\Lc{input} commands: ]
There is a bug in the expansion of \Lc{input} commands which causes 
a problem
when more than one \Lc{input} command appears on the same line.
There is no quick fix other than suggesting that you put each
\Lc{input} command on a line by itself,
in the \LaTeX{} source files.

\item [\Lc{input} commands in \env{verbatim} environments: ]
\strikeout{These cause problems; there's no fix yet.}
Try using either the \env{verbatim} or the \env{verbatimfiles} package.


\item [Optional arguments in \env{description} environments: ]
If~you have optional arguments for the \Lc{item} command in 
a \env{description} environment containing nested ``\texttt{]}'' characters then 
these may not show up correctly. To avoid the problem enclose them
in \verb|{}|s;\\ e.g. \ \verb+\item[{[nested [angle [brackets] are ok]]}]+


\item [\latextohtml{} behaves differently even when you run it on the
same file: ]~\\
If~you notice any strange side-effects from previous runs of \latextohtml{}, 
try using the option \Lc{no\_reuse} and choose \texttt{(d)} when prompted. 
This will clear any intermediate files generated during previous runs.
Note that this option will disable the image-reuse mechanism.

\item [Cannot convert \PS\ images which are included
in the \LaTeX{} file: ]~\\
It~is likely that the macros you are using for including \PS\ 
files (e.g. \Lc{epsffile}) are not understood by \latextohtml.
To avoid this problem enclose them in an environment which will
be passed to \LaTeX{} anyway; e.g.
\begin{quote}
%begin{latexonly}
\begin{small}
%end{latexonly}
\Lc{begin}\verb|{figure}|\\
\Lc{epsffile}\verb|{|\Meta{PostScript file name}\verb|}|\\
\Lc{end}\verb|{figure}|
%begin{latexonly}
\end{small}
%end{latexonly}
\end{quote}

Another reason why this might happen is that your shell environment variable 
\fn{TEXINPUTS} may be undefined. This is not always 
fatal but if you have problems you can use full
path-names for included \PS\ files (even when the \PS\
files are in the same directory as the \LaTeX{} source file).
Alternatively try setting \fn{TEXINPUTS} to `\texttt{.::}'. 
With some \TeX{} and \LaTeX{} installations setting \fn{TEXINPUTS} to 
`\texttt{.::}' may cause problems in the normal operation of \LaTeX.
If you get errors such as \LaTeX{} complaining that it can no longer find
any style files then you must set \fn{TEXINPUTS} to 
\verb|"<path to your LaTeX installation>:."|
if you want to use both \LaTeX{} and \latextohtml{}.

\item [Some of the inlined images are in the wrong places: ]
There are several known ways that this may occur.
\begin{itemize}
\item
Perhaps one of the inlined images is more than a page (paper page) long. 
This is sometimes the case with very large tables
or large \PS\ images. In this case you can try specifying 
a larger paper size (e.g. `\texttt{a4}', `\texttt{a3}' or even `\texttt{a0}') 
instead of the default (`\texttt{a5}') 
using the \latextohtml{} variable \fn{\$PAPERSIZE} 
in the file \fn{latex2html.config}.

\smallskip\noindent
\textit{This reason for the error should no longer occur with \textsc{v97.1}\,.
Please report it on the mailing-list, if it does.}

\item
More likely is that some inappropriate \LaTeX{} code 
has caused an error, resulting in an extra page (or pages) being generated.
Examine the \fn{images.log} file, to see if it reports any \LaTeX{} errors.

\item
A much rarer reason is that by default the \fn{dvips} program
reverses the \PS\ pages it generates. If your \fn{dvips} program
behaves in this way try changing the line: \html{\\}
\verb|$DVIPS = "dvips";| \html{\\}
to: \html{\\}
\verb|$DVIPS = "dvips -r0";| \html{\\}
within the file \fn{latex2html.config}.

\item
Yet another reason for images appearing out of place, especially while
developing a document, is that the browser's image cache is providing
out-of-date versions rather than getting the latest version afresh.
When this occurs there will often be images stretched or shrunk
to fit the wrong sized imaging area; this symptom is browser-dependent.
Flushing the cache, then reloading the \texttt{HTML} document, should
clear up the problem. 
\end{itemize}


\item [\textbf{Unacceptable quality of converted images: }]
Try changing the size of the image 
(see \hyperref{image conversion}{Section~}{}{imgcon}).

\item [The bibliographic references are missing: ]
Run \fn{latex} and then \fn{bibtex} on the original source file in
order to generate a \texttt{.bbl } file. 
\latextohtml{} may need the \texttt{.bbl } file in order to generate 
the references.


\item [The labels of figures, tables or equations are wrong: ]
This can happen if you have used any figures, tables, equations or
any counters inside conditional text; i.e. in a \env{latexonly} 
or a \env{htmlonly} environment. 


\item [Problems after changing the configuration files: ]
Please make sure that the last line in the configuration files 
(i.e. \fn{.latex2html-init} and \fn{latex2html.config}) is:
\begin{small}
\begin{verbatim}
1;	# This is the last line
\end{verbatim}
\end{small}
This is a \Perl{} quirk.

\item [Problems when producing the \texttt{.dvi} version: \label{htmlsty}]
If you are using any of the new \LaTeX{} commands which are defined in 
the \fn{html.sty} file make sure that \fn{html.sty} is included;
e.g. as one of the optional arguments to the \Lc{documentclass} command.

Of course you also have to make sure that \LaTeX{} knows where the \fn{html.sty}
file is, either by putting it in the same place as the other style-files on
your system, or by changing your \fn{TEXINPUTS} shell environment variable%
\footnote{If don't know how to do either of these things, copy (or link) \fn{html.sty} 
to the directory of your \LaTeX{} document.}.

\item [Some of the fonts are translated incorrectly: ]
There is a fault in way the \LaTeX{} scoping rules have been 
interpreted in \latextohtml. Consider this:
\begin{small}
\begin{verbatim}
\ttfamily fixed-width font.
\begin{something}
nothing here
\end{something}
default font.
\end{verbatim}
\end{small}
When processed by \LaTeX, the effect of the \Lc{tt} command is
delimited by the beginning of the environment ``something'',
so that ``default font'' will appear in the default font. 
But \latextohtml{} will not recognise
``something'' as a delimiter and ``default font'' will appear in the
wrong font. 

To avoid this problem (until it is fixed) you may delimit the scope of
some commands explicitly using \verb|{}|'s; i.e.
\begin{small}
\begin{verbatim}
\texttt{fixed-width font}.
\begin{something}
nothing here
\end{something}
default font.
\end{verbatim}
\end{small}

\item [Using \appl{Ghostscript 3.x} it no
longer generates inlined images for equations:] \hfil\\
If~you have a version of \latextohtml{} later than 0.6.1, go to the
\latextohtml{} directory and run \fn{install-test} again. 
This should fix it.

With earlier versions of \latextohtml{} you can fix it by 
replacing the file \fn{pstoppm.ps} in the 
\latextohtml{} directory with a newer one that accompanies 
\appl{Ghostscript 3.x}.\\ 
Alternatively you can avoid using \fn{pstoppm.ps} 
by changing the way \texttt{GS} is invoked in the file \fn{pstogif},
using something like: \\
\verb/open (GS, "|$GS -q -sDEVICE=ppmraw -sOutputFile=$base.ppm $base.ps");/

\item [Cannot get it to generate inlined images: ]
Try a small test file; e.g.
\begin{small}
\begin{verbatim}
% image-test.tex
\documentstyle{article}
\begin{document}
Some text followed by \fbox{some more text in a box}.
\end{document}
\end{verbatim}
\end{small}

You should see something like:
\begin{small}
\begin{verbatim}
This is LaTeX2HTML Version  (Wed Dec 1 1993) by Nikos Drakos, 
Computer Based Learning Unit, University of Leeds.

OPENING /usr/cblelca/nikos/scripts/tex2html/tests/image-test.tex 

Reading ....
Translating ...0/1.....1/1......
Generating images using latex ...
This is TeX, C Version 3.14t3
12222_images.tex
LaTeX Version 2.09 <7 Dec 1989>

Generating postscript images using dvips ...
This is dvips 5.521 Copyright 1986, 1993 Radical Eye Software
\end{verbatim}
\begin{verbatim}
' TeX output 1993.12.03:1050' -> 12222_image
(-> 12222_image001) <tex.pro>[1] 
Initializing... done.
Ghostscript 2.6.1 (5/28/93)
Copyright (C) 1990-1993 Aladdin Enterprises, Menlo Park, CA.
  All rights reserved.
Ghostscript comes with NO WARRANTY: see the file COPYING for details.
GS>GS>Writing 12222_image001.ppm
GS>pnmcrop: cropping 119 rows off the top
pnmcrop: cropping 961 rows off the bottom
pnmcrop: cropping 208 cols off the left
pnmcrop: cropping 484 cols off the right

Doing section links .....
Done.
\end{verbatim}
\end{small}


If there is a problem somewhere during the conversion from \PS\ 
to an image-format then you can try to do it manually,
so that you can find out where the problem is. 
Here is one way to do it (Please use the \fn{pstoppm3.ps}
file instead of \fn{pstoppm.ps} if your version of \appl{Ghostscript} is
later than 3.0):
%
\begin{small}
\begin{verbatim}
cblelca% latex image-test.tex
This is TeX, C Version 3.14t3
(image-test.tex
LaTeX Version 2.09 <7 Dec 1989>
(/usr/TeX/tex.lib/inputs/paper.sty
Document Style `paper' <28 Nov 89>.
(/usr/TeX/tex.lib/inputs/pap11.sty) 
(/usr/TeX/tex.lib/inputs/doublespace.sty)
(/usr/TeX/tex.lib/inputs/smaller.sty)) 
(/usr/TeX/tex.lib/inputs/psfig.sty
psfig/tex 1.9
)
No file image-test.aux.
[1] (image-test.aux) )
Output written on image-test.dvi (1 page, 652 bytes).
Transcript written on image-test.log.
cblelca% dvips -o image-test.ps image-test.dvi
\end{verbatim}
\begin{verbatim}
This is dvips 5.519 Copyright 1986, 1993 Radical Eye Software
' TeX output 1993.11.12:1412' -> image-test.ps
<tex.pro>. [1] 
cblelca% gs -dNODISPLAY pstoppm.ps
Initializing... done.
Ghostscript 2.6.1 (5/28/93)
Copyright (C) 1990-1993 Aladdin Enterprises, Menlo Park, CA.
  All rights reserved.
Ghostscript comes with NO WARRANTY: see the file COPYING for details.
GS>(image-test) ppm1run 
Writing image-test.ppm
GS>quit
cblelca% pnmcrop image-test.ppm >image-test.crop.ppm
pnmcrop: cropping 61 rows off the top
pnmcrop: cropping 110 rows off the bottom
pnmcrop: cropping 72 cols off the left
pnmcrop: cropping 72 cols off the right
cblelca% ppmtogif image-test.crop.ppm >image-test.gif
\end{verbatim}
\end{small}

\item [STILL cannot get it to generate inlined images for equations, etc. ]
If you have no problems with the \fn{image-test.tex} file but you
still cannot convert the images in some of your files 
have a look in the directory of the generated
\texttt{HTML} files for two files \fn{images.tex} and \fn{images.log}. Do you notice
anything unusual in them? Copy \fn{images.tex} in the directory 
of your original \LaTeX{} file and run \fn{latex} on \fn{images.tex}.
Can you see any errors in \fn{images.log}? If yes can you fix
\fn{images.tex} to get rid of the errors? 
After fixing \fn{images.tex}
you can put it back in the directory of \texttt{HTML} files created by
\latextohtml{} and run \latextohtml{} on the original document 
using the option \Cs{images\_only}. 

If you get into a mess try running \latextohtml{} with the options
\Cs{no\_reuse} and \Cs{no\_images}; e.g.
\begin{small}
\begin{verbatim}
cblipca% latex2html -no_reuse -no_images test.tex
This is LaTeX2HTML Version 95 (Tue Nov 29 1994) by Nikos Drakos, 
Computer Based Learning Unit, University of Leeds.

OPENING /tmp_mnt/home/cblelca/nikos/tmp/test.tex 
Cannot create directory /usr/cblelca/nikos/tmp/test: File exists
(r) Reuse the images in the old directory OR
(d) *** DELETE *** /usr/cblelca/nikos/tmp/test AND ITS CONTENTS OR
(q) Quit ?
:d

Reading ...
Processing macros ....+.
Reading test.aux ......................
Translating ...0/1........1/1.....
Writing image file ...

Doing section links .....

*********** WARNINGS ***********

If you are having problems displaying the correct images with Mosaic,
try selecting "Flush Image Cache" from "Options" in the menu-bar 
and then reload the HTML file.

Done.
\end{verbatim}
\end{small}
Then try to have a look in the file  \fn{images.tex} 
(as described earlier) and perhaps fix it.
Once you are happy that \fn{images.tex} is OK, run \latextohtml{}
again with the option \Cs{images\_only}.
The options \Cs{no\_reuse}, \Cs{no\_images} and \Cs{images\_only}
are available with \latextohtml{} version 0.7 or later.

Some problems in displaying the correct inlined images,
may be due to the image caching mechanisms of your browser.
With some browsers a simple ``\textbf{Reload Current Document}'' will be enough
to refresh the images but with others (e.g. \appl{Mosaic}) you may need
to request for the cache to be refreshed. With \appl{Mosaic} try 
selecting ``\textbf{Flush Image Cache}'' from ``\textbf{Options}'' in the menu-bar 
and then reload the \texttt{HTML} file.


\item [It cannot do slides, memos, etc. ] 
If you use Sli\TeX{} you can go a long way just by replacing 
the \verb|{slides}| argument of the \Lc{documentclass} command with 
something like \verb|{article}| just before using \latextohtml.
One problem may be that all your slides will end up in the  same \texttt{HTML} 
file.
If you use \fn{lslide.sty} you may get much better results 
(\htmladdnormallinkfoot{use \appl{Archie}}{http://www.pvv.unit.no/archie/} 
to find this or any other style files).
\end{htmllist}
\index{problems|)}

