From: Christoph Redecker <christoph.redecker@tu-harburg.de>
To: ntg-context@ntg.nl
Subject: Re: tikz / pgf 2.10: errors
Date: Wed, 27 Apr 2011 19:44:03 +0200 [thread overview]
Message-ID: <4DB855E3.4070106@tu-harburg.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1104270418590.14235@ybpnyubfg.ybpnyqbznva>
I'm currently installing the minimals (again) using the command line. I
unzipped the contents of the zip file to a directory (without spaces)
and started first-setup.bat (no argument, so I'm getting the current beta?).
It is now going through a list of font files (that's what I see in the
window) and in the meantime I made a copy of kpathsea601.dll in the bin
directory and renamed it to kpathsea600.dll. I'm still waiting for
something to happen...
It finished without errors! Running setuptex.bat throws no message at
all, I suppose this means that it finished successfully.
What's next? I don't want to break anything by just trying to "use"
context, I'm afraid of skipping something important now.
Regards
Christoph
On 27.04.2011 10:24, Aditya Mahajan wrote:
> On Wed, 27 Apr 2011, Christoph Redecker wrote:
>
>> For the gui installer, I provided what I could. I clicked "Next" and
>> "Finish" where I could, but the options I used are included in my last
>> post. Is it possible that you mixed up the command line installation
>> and the gui variant?
>
> Yes I did mix the two up. I re-read your last post again. I don't know
> why you get the missing kpathsea600.dll error message. The bin directory
> actually contains kpathsea601.dll.
>
> Aditya
>
> ___________________________________________________________________________________
>
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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 prev parent reply other threads:[~2011-04-27 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 11:45 Christoph Redecker
2011-04-26 12:22 ` Hans Hagen
2011-04-26 13:49 ` Christoph Redecker
2011-04-26 19:32 ` Christoph Redecker
2011-04-26 19:43 ` Aditya Mahajan
2011-04-27 7:36 ` Christoph Redecker
2011-04-27 8:24 ` Aditya Mahajan
2011-04-27 8:32 ` Christoph Redecker
2011-04-27 17:44 ` Christoph Redecker [this message]
2011-04-27 17:53 ` Hans Hagen
2011-04-27 18:12 ` Aditya Mahajan
2011-04-27 18:38 ` Christoph Redecker
2011-04-28 15:20 ` Mojca Miklavec
2011-04-28 15:30 ` Mojca Miklavec
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=4DB855E3.4070106@tu-harburg.de \
--to=christoph.redecker@tu-harburg.de \
--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).