Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Great confusion ....

13 views
Skip to first unread message

Iraklis Nikolakakos

unread,
Jun 1, 2000, 3:00:00 AM6/1/00
to
Hi all,
I am a newbi here and I have some trivial problems. But now the
problem is serious, since I can't even run latex and I can't proceed
with writting my final thesis. So I am in great need of help:
The problem (I 'll try to describe it) is as follows:
I can't find why but this morning ,after I had tried to install a new
package,
I gave in ms-dos :
c:\h\diplomatiki\latex sample2.tex
and I got:
This is Tex version 3.14159 (MikTex 1.20d)
-C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
initexmf: don't known how to dump LATEX
I can't find the default format file

After I realized that something was wrong and I tried to run maintenance
files.
I run : Create all format files and I got (in a ms-dos window):
...
Transcript written on latex.log
INITEXMF: etex.exe failed on latex

I tried to find the latex.log file but it was nowhere.

I did the same with Create LaTeX format file and I got:
Transcript written on latex.log
INITEXMF: tex.exe failed on latex

I tried to find the latex.log file but it was again nowhere.

Please, send me your ideas or refer me to a source where I could
read about these matters as soon as possible,
Thanks in advance,

Iraklis


Dan Luecking

unread,
Jun 1, 2000, 3:00:00 AM6/1/00
to
In article <8h561h$2m96$1...@ulysses.noc.ntua.gr>, "Iraklis

Nikolakakos" <el9...@central.ntua.gr> wrote:
>Hi all,
>I am a newbi here and I have some trivial problems. But now the
>problem is serious, since I can't even run latex and I can't
proceed
>with writting my final thesis. So I am in great need of help:
>The problem (I 'll try to describe it) is as follows:
>I can't find why but this morning ,after I had tried to install
a new
>package,
>I gave in ms-dos :
>c:\h\diplomatiki\latex sample2.tex
>and I got:


What is this program \h\diplomatiki\latex? I presume it is
a batch file. What is in it?

In a MiKTeX system, the latex executable is
\texmf\miktex\bin\latex.exe

>This is Tex version 3.14159 (MikTex 1.20d)
>-C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
>initexmf: don't known how to dump LATEX
>I can't find the default format file

This is obviously mistyped. You should try to get the error
messages exactly.

>
>After I realized that something was wrong and I tried to run
maintenance
>files.
>I run : Create all format files and I got (in a ms-dos window):

>....


>Transcript written on latex.log
>INITEXMF: etex.exe failed on latex
>

Some possiblities:
(1) MiKTeX was incompletely or incorrectly installed.
(2) You have a file named latex.tex somewhere in your LaTeX
search path. Perhaps in the package you installed?
If such a file exists, initexmf will try to
use it in creating a format. If it doesn't exist,
initexmf will create a temporary file latex.ini whose
job is to input latex.ltx.

To correct (1) you can reinstall MiKTeX. Iif you do, maybe
you should update to version 1.20e.

To correct (2), find the errant file with
initexmf --find-tex-input latex.tex
and/or
initexmf --find-etex-input latex.tex
and either delete it or rename it or move it out of the search
path(s).

>I tried to find the latex.log file but it was nowhere.

initexmf --dump=<whatever>" will always delete the log files.
(I don't like that either, but normally it's OK.

If you want to keep the .log file, create the format by hand
as follows

for LaTeX:
tex --ini latex.ltx \dump
for elatex:
etex --ini latex.ltx \dump

>
>I did the same with Create LaTeX format file and I got:
>Transcript written on latex.log
>INITEXMF: tex.exe failed on latex
>

Same possible problems and fixes.

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!


Marco Lucisano

unread,
Jun 3, 2000, 3:00:00 AM6/3/00
to
Iraklis Nikolakakos <el9...@central.ntua.gr> wrote in message
news:8h561h$2m96$1...@ulysses.noc.ntua.gr...

> c:\h\diplomatiki\latex sample2.tex
> and I got:
> This is Tex version 3.14159 (MikTex 1.20d)
> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
> initexmf: don't known how to dump LATEX
> I can't find the default format file

Hi!
I do get exactly the same error message (and it is definitely not mistyped)
after installing a new package (subfigure in my case). I reinstalled
everything and got the same error as soon as I tried to install subfigure -
It works fine with every other package I have installed so far. Any
suggestion is highly appreciated. Thanks.

Marco


-----------------------------------------------------------------
Marco Lucisano
e-mail: marco.l...@chello.se
ICQ# 50071752
-----------------------------------------------------------------

Robin Fairbairns

unread,
Jun 3, 2000, 3:00:00 AM6/3/00
to
Marco Lucisano <marco.l...@starport.se> wrote:
>Iraklis Nikolakakos <el9...@central.ntua.gr> wrote...

>> c:\h\diplomatiki\latex sample2.tex
>> and I got:
>> This is Tex version 3.14159 (MikTex 1.20d)
>> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
>> initexmf: don't known how to dump LATEX
>> I can't find the default format file
>
>I do get exactly the same error message (and it is definitely not mistyped)
>after installing a new package (subfigure in my case). I reinstalled
>everything and got the same error as soon as I tried to install subfigure -
>It works fine with every other package I have installed so far. Any
>suggestion is highly appreciated. Thanks.

one of the above is wrong: maybe the command line that's quoted.

i thought (not being a miktex user) that initexmf was to do with
installing the system, not sticking a package onto the texmf tree.
from the diagnostic, that sounds to be the case ... really.

i'm told that miktex documentation is quite good: i suggest you have a
dig into it to find about installing new packages.
--
Robin Fairbairns, Cambridge

Andreas Luebbecke

unread,
Jun 4, 2000, 3:00:00 AM6/4/00
to
Marco Lucisano schrub:

>> This is Tex version 3.14159 (MikTex 1.20d)
>> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
>> initexmf: don't known how to dump LATEX
>> I can't find the default format file
>

> Hi!


> I do get exactly the same error message (and it is definitely not
> mistyped) after installing a new package (subfigure in my case). I
> reinstalled everything and got the same error as soon as I tried
> to install subfigure - It works fine with every other package I
> have installed so far. Any suggestion is highly appreciated.

I just read about a simliar problem in de.comp.text.tex, where a guy
got the same error message after installing the old 1.20d for the
first time.
He was told to set his system date back to June 99 for initexmf, and
reset it to current date afterwards, and it helped him.

Andreas
--
Filtern statt füttern.

Dan Luecking

unread,
Jun 4, 2000, 3:00:00 AM6/4/00
to
In article <8hbtcq$b47$1...@pegasus.csx.cam.ac.uk>,

r...@betsy.cl.cam.ac.uk (Robin Fairbairns) wrote:
>Marco Lucisano <marco.l...@starport.se> wrote:
>>Iraklis Nikolakakos <el9...@central.ntua.gr> wrote...
>>> c:\h\diplomatiki\latex sample2.tex
>>> and I got:
>>> This is Tex version 3.14159 (MikTex 1.20d)
>>> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
>>> initexmf: don't known how to dump LATEX
>>> I can't find the default format file
>>
>>I do get exactly the same error message (and it is definitely
not mistyped)
>>after installing a new package (subfigure in my case). I
reinstalled
>>everything and got the same error as soon as I tried to install
subfigure -
>>It works fine with every other package I have installed so far.
Any
>>suggestion is highly appreciated. Thanks.
>
>one of the above is wrong: maybe the command line that's quoted.
>
>i thought (not being a miktex user) that initexmf was to do with
>installing the system, not sticking a package onto the texmf
tree.
>from the diagnostic, that sounds to be the case ... really.

Normally initexmf is used for everything, many users run it from
the Windows Start Menu, where, under
"Programs|MiKTeX|Maintenance" there are 4 choices, each running
initexmf with different options. Many users, when they only need
to select "refresh filename database", routinely select
"reconfigure" (which does that, but also dumps all the known
formats).

The spelling "LaTeX" is odd, since "initexmf -dump=latex" (lower
case) is the command to redo the LaTeX format, and the error
message should echo the same word ("LaTeX" not "LATEX").
Moreover, simply invoking latex should not trigger initexmf or
any messages from it. That's why I suggested there was a latex
batch file being accidentally invoked, and/or a latex.tex file
inadvertently left in the input path, and/or a somewhat incorrect
installation..

Dan Luecking

unread,
Jun 4, 2000, 3:00:00 AM6/4/00
to
In article <8hbrrv$aj$1...@zingo.tninet.se>, "Marco Lucisano"

<marco.l...@starport.se> wrote:
>Iraklis Nikolakakos <el9...@central.ntua.gr> wrote in message
>news:8h561h$2m96$1...@ulysses.noc.ntua.gr...
>> c:\h\diplomatiki\latex sample2.tex
>> and I got:
>> This is Tex version 3.14159 (MikTex 1.20d)
>> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX
>> initexmf: don't known how to dump LATEX
>> I can't find the default format file
>
>Hi!

>I do get exactly the same error message (and it is definitely
not mistyped)

Really? It says "intexmf" and not initexmf? It capitalizes LaTeX
(LATEX) in two different ways? It has two spaces between "don't"
and "know"? That's why I said the original poster must have
mistyped the message. In dealing with computer programs, such
little things often count.

Iraklis Nikolakakos

unread,
Jun 5, 2000, 3:00:00 AM6/5/00
to
> Really? It says "intexmf" and not initexmf? It capitalizes LaTeX
> (LATEX) in two different ways? It has two spaces between "don't"
> and "know"? That's why I said the original poster must have
> mistyped the message. In dealing with computer programs, such
> little things often count.
>
Dan is right. Actually the exact message was:

This is Tex version 3.14159 (MikTex 1.20d)
-C:\texmf\miktex\bin\initexmf.exe --dump=LATEX

initexmf: don't known how to dump LATEX
I can't find the default format file

In addition I should have said that c:\h\diplomatiki\latex was just
the path of the directory where I run latex, not a batch file.
Anyway, I tried to reinstall MikTex but the problem persisted. I tried
to find out what was wrong about the dump files through the manual of
MikTeX but I couldn't. Still I am interested about what was the problem.
Why the error message given LATEX and not latex?
At last I was given a new edition (beta) of latex : TeXLive, and I can
proceed
with my final thesis. I could say that now is better than before, taking
into
account a lot of things (friendliness, windvi, texshell, etc.).
Thanks for your help.

Iraklis


Ichimusai

unread,
Jun 5, 2000, 3:00:00 AM6/5/00
to
In reply to what Andreas....@gmx.de (Andreas Luebbecke) posted in
article <8hdnu...@luebbecke.fqdn.th-h.de> on 4 Jun 2000 12:08:44 GMT to
comp.text.tex about Re: Great confusion ....

> I just read about a simliar problem in de.comp.text.tex, where a guy
> got the same error message after installing the old 1.20d for the
> first time.
> He was told to set his system date back to June 99 for initexmf, and
> reset it to current date afterwards, and it helped him.

I ran into the same problem today. I just reinstalled my workstation and did
not have the time to grab the latest dist of MikTeX 1.20 to stick it on, so I
grabbed an old download from the local fileserver that was downloaded some
six months ago or so.

I installed, restarted, ran the configuration scripts and ended up with the
same problem, now, I did not bother to set the clock back, because I could
not figure out what was the real problem here, but I noticed that several
programs during configuration complained that the distribution was old so I
am in the process of downloading a fresh dist right now.

I hope it works. It should. MikTeX is usually quite easy to install.

--
AA #769, ICQ 1645566, Yahoo Ichimusai, PGP key <krikk...@algonet.se>
Home http://ichimusai.welcome.to/ http://www.algonet.se/~krikkit/nyasajten
EAC Research Coordinator - It's a thankless job, but I've got Karma to burn
Dii minore, numquam se minus solum quam cum solus esset. Respice post te,
mortalem te esse memento---carpe diem!

Jeffrey Goldberg

unread,
Jun 5, 2000, 3:00:00 AM6/5/00
to
On Jun 4, 2000 Dan Luecking <luecking...@comp.uark.edu.invalid> wrote:

> In article <8hbrrv$aj$1...@zingo.tninet.se>, "Marco Lucisano"
> <marco.l...@starport.se> wrote:
> >Iraklis Nikolakakos <el9...@central.ntua.gr> wrote in message
> >news:8h561h$2m96$1...@ulysses.noc.ntua.gr...
> >> c:\h\diplomatiki\latex sample2.tex
> >> and I got:

> >> This is Tex version 3.14159 (MikTex 1.20d)

> >> -C:\texmf\miktex\bin\intexmf.exe --dump=LaTeX


> >> initexmf: don't known how to dump LATEX
> >> I can't find the default format file
> >

> >Hi!
> >I do get exactly the same error message (and it is definitely
> not mistyped)
>

> Really? It says "intexmf" and not initexmf? It capitalizes LaTeX
> (LATEX) in two different ways? It has two spaces between "don't"
> and "know"?

Take a second look. That is two spaces between "don't" and
"known".
^<--- another typo

Now maybe that is a genuine error message reported faithfully, but if
so then it certainly isn't any knowed TeX system running.

-j

--
Jeffrey Goldberg
Note: I am moving and changing many addresses, please see
http://www.goldmark.org/jeff/contact.html
Relativism is the triumph of convention over truth, authority over justice


Dan Luecking

unread,
Jun 5, 2000, 3:00:00 AM6/5/00
to
In article <XOk7Obiv7pTWX+...@4ax.com>, Ichimusai

Here's a possibility: MiKTeX installs a few .dll's. In the past
(and I don't know when the change occured) it installed some only
in the windows/system directory. Currently there is at least one
(msvcrt.dll) that is installed in both the system directory and
in the texmf\miktex\bin directory. It is possible, if 1.20d is
installed over 1.20e, that programs expecting one version of some
dll are encountering another version. And conversely, .dll's
expecting to be running in one version find files from another.

There are also possible registry entries held over from one
install to the next.

If this is the case, one would be advised to read the readme
about uninstalling MiKTeX and follow it: remove a few entries
from the registry and delete the entire main texmf tree, before
installing a different version. (Especially when installing and
old one over a new.)

In particular, when 1.20 came out it was strongly suggested that
any 1.1 or earlier version be completely removed.

Ichimusai

unread,
Jun 8, 2000, 3:00:00 AM6/8/00
to
In reply to what Dan Luecking <luecking...@comp.uark.edu.invalid> posted
in article <00afb61f...@usw-ex0102-084.remarq.com> on Mon, 05 Jun 2000
13:51:33 -0700 to comp.text.tex about Re: Great confusion ....

> Here's a possibility: MiKTeX installs a few .dll's. In the past
> (and I don't know when the change occured) it installed some only
> in the windows/system directory. Currently there is at least one
> (msvcrt.dll) that is installed in both the system directory and
> in the texmf\miktex\bin directory. It is possible, if 1.20d is
> installed over 1.20e, that programs expecting one version of some
> dll are encountering another version. And conversely, .dll's
> expecting to be running in one version find files from another.

> There are also possible registry entries held over from one
> install to the next.

However, my install of MikTeX was on a completely fresh system, there was no
old stuff present, no DLLs or registry settings.

> If this is the case, one would be advised to read the readme
> about uninstalling MiKTeX and follow it: remove a few entries
> from the registry and delete the entire main texmf tree, before
> installing a different version. (Especially when installing and
> old one over a new.)

That is always a good advice.

> In particular, when 1.20 came out it was strongly suggested that
> any 1.1 or earlier version be completely removed.

Yes, but this problem is something that goes wrong when creating the format
files, the error message when trying to compile is that the default format
file can't be found.

Dan Luecking

unread,
Jun 8, 2000, 3:00:00 AM6/8/00
to
In article <B80+OXUwHrAZbH...@4ax.com>, Ichimusai

<ic...@earthling.net> wrote:
>In reply to what Dan Luecking
<luecking...@comp.uark.edu.invalid> posted
>in article <00afb61f...@usw-ex0102-084.remarq.com> on Mon,
05 Jun 2000
>13:51:33 -0700 to comp.text.tex about Re: Great confusion ....
>
>Yes, but this problem is something that goes wrong when creating
the format
>files, the error message when trying to compile is that the
default format
>file can't be found.

I was just throwing out possibilities. The most likely one (in my
opinion) is one I mentioned in my first reply: that the latex
format failed to make because there is some file latex.tex in the
TeX search path which is being input by initex (it will do this
only if latex.tex exists, otherwise it will use latex.ini, which
it will create if it doesn't exist). In a clean new MiKTeX
system, there is no latex.tex. It is, however, a key component of
the obsolete LaTeX209. Also, I have seen it as the name of a
documentation file for some packages (packages that are intended
fro plainTeX sometimes include instructions on how to adapt them
to LaTeX).

Do you (or did you) have such a file?

Dan Luecking

unread,
Jun 12, 2000, 3:00:00 AM6/12/00
to
In article <8i2f88$4e8$1...@pegasus.csx.cam.ac.uk>,
r...@pallas.cl.cam.ac.uk (Robin Fairbairns) wrote:
>Ichimusai <ic...@earthling.net> wrote:
>>I just tried it on another machine, and the installation fails.
If I set the
>>clock back to June 1999 it works. Interesting.
>>
>>Something fails when the init outputs its warnings that the
release is old.
>>I've not yet had the time to investigate the logs properly, but
something
>>messes up the creation of several .fmt files.
>
>they're not warnings: they're error messages; the formats aren't
>created because the code is set up not to create an old format
without
>manual intervention.

Well, the manual intervention is slight: you have to press
[enter] to scroll by the error message and a perfectly usable
format file is created.

On the other hand, configuration utilities like MiKTeX's may
check the error code and report a failure. And clean up by
discarding the resultant format file and the .log file. This is
the really serious failing: if the .log file were retained after
the failure, the "Great Confusion" could be considerably less
than "great".

This setting the clock back may work, but the best bet is to
update LaTeX, which in MiKTeX could be accomplished by updating
to MiKTeX 1.20e.

Giuseppe Bilotta

unread,
Jun 16, 2000, 3:00:00 AM6/16/00
to
Dan Luecking <luecking...@comp.uark.edu.invalid> wrote

Don't think so; there have been messages in the MiKTeX ml about the same
problem; maybe, wait for MiKTeX 2.0, dued in July, or simply take the last
LaTeX from CTAN

--
Giuseppe Bilotta
bour...@bigfoot.com

=============================================
This paper contains much that is new and much that is true.
Unfortunately, that which is true is not new
and that which is new is not true.
(Wolfgang Pauli (attr.))
=============================================

0 new messages