Mail Archives: djgpp/2000/01/10/12:00:39
On Mon, 10 Jan 2000 davin_pearson AT yahoo DOT com wrote:
> I am trying to install TeX on my Windows 95
> computer at home and am running into some
> troubles getting the font creation to work.
This analysis is correct: your problem is that METAFONT fails to
create missing fonts.
> ' TeX output 2000.01.09:2048' -> PRN
> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi
> 600 cmr10
> running mf: No such file or directory (ENOENT)
This is the first sign of trouble: mktexpk tried to invoke METAFONT,
but failed. The error message ("No such file or directory") is
strange: it means that mktexpk couldn't read the output file produced
by METAFONT. Why? Mystery number 1.
> mktexpk: Mismatched mode ljfour and resolution 600; ignoring mode.
This is a result of the previous failure: METAFONT was called to
determine the required mode and resolution; since it failed, mktexpk
now falls back to the default values (the error message is slightly
misleading).
> This is METAFONT, Version 2.718 (Web2C 7.2)
> I can't find the base file `MF.base'!
Another problem: METAFONT cannot find the file MF.base. This file
comes with webc72b.zip and unzips into the share/texmf/web2c
directory; please make sure it is there on your system.
> mktexpk: warning: can't open log file cmr10.log.
Huh? How come mktexpk cannot open a file? Mystery number 2.
> C:/DJGPP/BIN/dvips.exe: Font cmr10 not found, characters will be left
> blank.
Why is "C:/DJGPP/BIN" printed in upper case, but with forward slashes?
Did you invoke dvips from Bash?
> The LaTeX'ing worked fine without any errors.
This doesn't prove anything: LaTeX doesn't need any fonts to be
created, since it doesn't actually produce any display or printout.
> I am installing TeX on behalf of someone else as well so
> help would be much appreciated!
My first guess would be that the target system doesn't have enough
available file handles. This would explain why METAFONT cannot open
MF.base (if it indeed is installed on that machine) and why the
logfile cmr10.log couldn't be created. It also explains why the first
invocation of METAFONT failed: its standard output is redirected to a
file, and if the file open call fails, the invocation will also fail.
So please see how many files simultaneously can that system have, and
if this is indeed a problem, bump up the number in the FILES=
directive in CONFIG.SYS.
- Raw text -