From: "Joel Black" <jwblack@ozemail.com.au>
To: <ntg-context@ntg.nl>
Subject: No file 'mpx314.aux'
Date: Sun, 1 Nov 2009 14:48:27 +1100 [thread overview]
Message-ID: <ED117A985D81442A8A4CD6335D6F22E5@ownerPC> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 965 bytes --]
I have written a Venn diagram metapost file, which I successfully ran on Troy Henderson's metapost previewer while at work.
prologues:=3;
verbatimtex
%&latex
\documentclass{minimal}
\begin{document}
etex
beginfig(1);
draw (0,0)--(200,0)--(200,160)--(0,160)--(0,0);
draw fullcircle scaled 80 shifted (80,80);
draw fullcircle scaled 80 shifted (120,80);
label.lrt (btex $\xi$ etex,(0,160));
label.lrt (btex $A$ etex, (40, 120));
label.llft (btex $B$ etex,(160,120));
endfig;
end;
However, now that I am working on it at home, the error message "no file 'mpx314.aux'" appears when I try to compile it. I have tried it on my older system (Miktex 2.6 running on Vista) and on my laptop (Miktex 2.8 running on Vista Home Premium). Actually, on the laptop I also get a popup telling me that "dvitomp.exe has stopped working" and directing me to the Windows update page. Am I doing something silly, or is this a bug, or what? Thanks kindly.
Joel.
[-- Attachment #1.2: Type: text/html, Size: 2198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2009-11-01 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 3:48 Joel Black [this message]
2009-11-01 7:22 ` Taco Hoekwater
2009-11-01 9:43 ` Joel Black
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=ED117A985D81442A8A4CD6335D6F22E5@ownerPC \
--to=jwblack@ozemail.com.au \
--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).