ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: long texexec run
Date: Thu, 11 Oct 2001 09:06:25 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20011011085326.0236e4b0@server-1> (raw)
In-Reply-To: <006501c151bf$2bb37870$695f298d@fhwolfenbuettel.de>

At 09:09 PM 10/10/2001 +0200, Karsten Hachmeister wrote:
>Hi,
>
> > How fast is your machine ?
>
>I am using a 700MHz Pentium III here. I reinstalled now an old version of
>miktex because of some other problems, but now I can give you some times:
>on the older miktex version the texexec run needed about 10 - 14 sec and
>with the new version I needed 66 - 68 sec for one texexec run.
>
>Another problem is that when I use TeXnicCenter to create my documents I get
>the error: texexec.ini not found
>The file exists and from the command line I can use the texexec command.
>This might be an error in TeXnicCenter, but with the older MiKTeX version I
>have no problems.

The number of pages per second depends on the complexity of the page. 
Documents with many menus (screen docs) and backgrounds that change per 
page take more time.

on my 1 gig laptop:

172 page mathml   manual (many buffers, color, xml included)    : 36 sec
  37 page examlpe  manual (xml, color, backgrounds, menus)       : 18 sec 
(13 sec in automp mode)
  76 page mathml   manual typeset as verbatim listing            :  5 sec
  75 page show-pre manual (372 pdf images+2 mp runs+fancy stuff) : 20 sec 
(18 sec in batch mode)

so, i think that there is something wrong with your setup. since 
texexec.ini cannot be found (you can try texexec --verbose to get more 
info) it looks like a file search problem.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  parent reply	other threads:[~2001-10-11  7:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 11:00 Karsten Hachmeister
2001-10-10 13:53 ` Hans Hagen
     [not found]   ` <006501c151bf$2bb37870$695f298d@fhwolfenbuettel.de>
2001-10-11  7:06     ` Hans Hagen [this message]
2001-10-11 10:41       ` Karsten Hachmeister
2001-10-11 11:37         ` Taco Hoekwater
2001-10-11 12:29           ` Karsten Hachmeister
2001-10-11 14:49             ` Hans Hagen
2001-10-11 20:02               ` Karsten Hachmeister
2001-10-12  6:59                 ` Hans Hagen
2001-10-12  9:16                   ` Eckhart Guthöhrlein
2001-10-12  9:50                     ` Taco Hoekwater
2001-10-12 14:07                     ` Karsten Hachmeister

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=5.1.0.14.1.20011011085326.0236e4b0@server-1 \
    --to=pragma@wxs.nl \
    --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).