ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: New Installation under miktex, not working
Date: Mon, 16 Jan 2006 09:10:49 +0100	[thread overview]
Message-ID: <6faad9f00601160010v6ce82033t284ecaaad78ead65@mail.gmail.com> (raw)
In-Reply-To: <5f8ls1llftg2hc0hvqhosfaquidc7u2fuu@4ax.com>

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:

I don't know why I keep using MikTeX (there are problems all the time,
but it is [or at least it should be] easy to update and is already
installed on most computers here), just some points:
- texexec --make --all doesn't work anyway (well, it works, but it
forgets to copy the files to the proper place)
If you want to make formats, go to MikTeX options -> TeX formats ->
choose cont-en -> Edit ...
Here are the values that I have (it may be that I changed any of them
manually, I don't remember):
Format Name: cont-en
Compiler: pdfe-TeX (Extended Mode)
Input File Name: cont-en.tex
Output File Name: cont-en.efmt
Exclude has to be unchecked

- MikTeX updates the formats automatically (if it does). If it
doesn't, the "standard ConTeXt" ways fail anyway and searching for
files doesn't always work either
- I often have problems after upgrading ConTeXt, but I can hardly tell
you what to do. I try all the different tricks (updating filename
database, building the formats, ...) without any success, but after
two days it simply works again by some black magic.

> <<
> texexec test.txt
>
>  TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
>
> unknown file type: texmfscripts
>  fixing texformat path : C:/localtexmf/miktex/fmt
> fixing engine variable : pdfetex
>
>         total run time : 0 seconds
> >>

That's the output that I get if the file doesn't exist.

Can you make a file "test.tex" (not txt) and try to compile that one?
Send the new report then (if there are any differences of course).

> texexec --version
> and
> <<
>  TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
>
> unknown file type: texmfscripts
>                texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE
> 1997-2005
>                texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE
> 1992-2004
>                    tex : pdfeTeX, 3.141592-1.21a-2.2 (MiKTeX 2.4)
> (preloaded format=cont-en 2006.1.15)  15 JAN 2006 11:32
>                context : ver: 2006.01.09
>                cont-en : ver: 2006.01.09  fmt: 2006.1.15  mes: english
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
>
>         total run time : 1 seconds

I also get this output since December (I thought that ConTeXt was
broken at first), but it is harmless and compiling the documents
nevertheless works. Perhaps that extensive use of "unknown file type:
'fmt'" is the new Taco's inclusion that Hans mentioned in some other
mail ;) "unknown file type: texmfscripts" should also be harmless and
will disapear once MikTeX starts to support the new pdfTeX (if I
understood correctly).

Mojca

  parent reply	other threads:[~2006-01-16  8:10 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
2006-01-16  8:10 ` Mojca Miklavec [this message]
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=6faad9f00601160010v6ce82033t284ecaaad78ead65@mail.gmail.com \
    --to=mojca.miklavec.lists@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).