From: Matthew Huggett <mhuggett@zam.att.ne.jp>
Subject: Re: building formats under MikTeX
Date: Wed, 06 Aug 2003 09:36:41 +0900 [thread overview]
Message-ID: <3F304D99.6010502@zam.att.ne.jp> (raw)
In-Reply-To: <5.2.0.9.1.20030805191222.02498290@server-1.pragma-net.nl>
Hans Hagen wrote:
> At 23:47 05/08/2003 +0900, you wrote:
>
>> Hello All:
>>
>> When I run texexec --make to (re)build my formats (under MikTeX),
>> texexec reports that it can't read TEX.POOL and MP.POOL . Then a
>> window's dialog box reports that pdfetex has crapped out. Any any
>> ideas?
>>
>> Thanks and best wishes,
>
>
>
> do you have the pool files?
>
> kpsewhich mp.pool
Yes, I have the files, but kpsewhich can't find them unless it's
actually run from the directory containing the files! I've updated the
databases but that doesn't help either. Also, when I process a tex
file, pdfetex can't find/open pdftex.cfg .
next prev parent reply other threads:[~2003-08-06 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 14:47 Matthew Huggett
2003-08-05 17:13 ` Hans Hagen
2003-08-06 0:36 ` Matthew Huggett [this message]
2003-08-06 1:11 ` darnold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F304D99.6010502@zam.att.ne.jp \
--to=mhuggett@zam.att.ne.jp \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).