From: Christopher G D Tipper <chris.tipper@gmail.com>
Subject: Re: New Installation under miktex, not working
Date: Sun, 15 Jan 2006 23:25:46 +0000 [thread overview]
Message-ID: <87EE85E5-BA13-45A0-A2AE-2D6B51E2A71F@gmail.com> (raw)
In-Reply-To: <43CABAA7.2060800@elvenkind.com>
Some defaults from my old MiKTeX .ini file (local-texmf/scripts/perl/
texexec.ini) I can't test this as I have defected to a saner
platform :-)
enable variable miktex at top of file and some variation of this below.
for miktex set UsedInterfaces to en, uk
for miktex set UserInterface to uk
for miktex set TeXExecutable to pdfetex.exe
for miktex set TeXVirginFlag to -initialize
for miktex set TeXBatchFlag to -interaction=batchmode
for miktex set TeXFormatFlag to &
for miktex set MpToTeXExecutable to mptotex.exe
for miktex set MpVirginFlag to -initialize
for miktex set MpPassString to
for miktex set MpBatchFlag to -interaction=batchmode
for miktex set MpFormat to metafun
for miktex set MpFormatFlag to -undump=
for miktex set TeXFormatPath to "d:\local-texmf\miktex\fmt\"
for miktex set ConTeXtPath to "d:\local-texmf\tex\context\base\"
for miktex set SetupPath to "c:\Progra~1\MiKTeX\miktek\base\"
for miktex set TeXScriptsPath to "d:\local-texmf\scripts\context
\perl\"
for miktex set TeXProgramPath to "c:\Progra~1\MiKTeX\miktex\bin\"
Also mptopdf will not work unless you set the TEXSYSTEM environment
variable to "miktex" as on ContextGarden.
Also it occurs to me that texexec will not recognise test.txt, but
will expect test and add .tex itself.
Don't forget to update fndb at every opportunity from MikTeX's
management app.
Christopher
> Todd DeVries wrote:
>> Hi,
>> I'm attempting to install context under miktex 2.4. I've updated the
>> format files and followed other instructions as per the contextgarden
>> discussions. I'm probably missing something really obvious and would
>> appreciate any help offered. I receive this output when running the
>> following commands:
>> <<
>> texexec test.txt
>
> Are you sure your tex file has extension txt? Your output is precisely
> what you get when texexec cannot find the input file, so I am a bit
> suspicious that that may be the problem.
>
> For the warnings: You need to tell texexec that you are running
> miktex, but I do not know how precisely that is done (I use tetex)
>
> Cheers, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
--------------------------------o00o--------------------------------
“Since light travels faster than sound, isn’t that why
some people appear bright until you hear them speak”
— Steve Wright
next prev parent reply other threads:[~2006-01-15 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 19:36 Todd DeVries
2006-01-15 21:12 ` Taco Hoekwater
2006-01-15 23:25 ` Christopher G D Tipper [this message]
2006-01-16 8:10 ` Mojca Miklavec
2006-01-16 15:35 ` Aditya Mahajan
2006-01-16 16:02 ` Mojca Miklavec
2006-01-17 6:23 ` Aditya Mahajan
2006-01-17 9:38 ` Hans Hagen
2006-01-16 17:15 ` Todd DeVries
2006-01-16 18:34 ` Ralph Roberts
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=87EE85E5-BA13-45A0-A2AE-2D6B51E2A71F@gmail.com \
--to=chris.tipper@gmail.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).