From: David Arnold <darnold@northcoast.com>
Subject: Re: MPtoPDF problem: metafun.mem error
Date: Tue, 19 Aug 2003 08:34:07 -0700 [thread overview]
Message-ID: <3.0.5.32.20030819083407.00b5d100@mail.northcoast.com> (raw)
In-Reply-To: <3714693859.20030819172848@ksk.ch>
Andreas,
First, type:
texexec --make --alone
and see what happens. Look in \localtexmf\miktex\fmt and check the dates of
cont-en.efmt. Look for a newly updated metafun.mem file. If there is one
there, move it to \localtexmf\miktex\mem.
On some systems texexec --make --alone will dumpt the format files into the
current directory. You must move them manually to the correct place:
\localtexmf\miktex\fmt for format files, \localtexmf\miktex\mem for the
metapost format files.
Don't forget to refresh the filename database and make sure Yap is closed
when you do so.
At 05:28 PM 8/19/03 +0200, you wrote:
>Hi,
>
> I'm trying to setup Metapost on my computer using Miktex (version
> 2.2.6) but when I try to execute mptopdf.pl I get the following
> error message:
>
><snip>
> TeXExec 3.2 - ConTeXt / PRAGME ADE 1997-2003
>
> metapost : G:\metapost\height
> format : metafun
>initexmf: don't know how to dump metafun
>cannot make metafun.mem
>I can't found the feault mem file!
>
> total run time : 0 seconds
>
>MPtoPDF 1.2 : error while processing mp file
></snip>
>
> I tried already different things (like changing paths) but nothing
> worked :(. How could I solve my problem?
>--
>Best regards,
> Andreas mailto:anstei@ksk.ch
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
next prev parent reply other threads:[~2003-08-19 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 15:28 Andreas Steiger
2003-08-19 15:34 ` David Arnold [this message]
2003-08-19 16:15 ` Re[2]: " Andreas Steiger
2003-08-27 17:25 ` Patrick Gundlach
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=3.0.5.32.20030819083407.00b5d100@mail.northcoast.com \
--to=darnold@northcoast.com \
--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).