> Thursday, December 11, 2003 Gary Pajer wrote: > > > MiKTeX. > > > I've done this half a dozen times. This time it doesn't work. I feel > > stupid. What have I forgotten? > > > Things were working perfectly. I decide to update, so I download > > cont-tmf.zip to \localtexmf. Then I unzip, overwritting all the old files. > > Then I update the database either using mktexlsr or the MiKTeX options > > wizard. > > > But now texexec can't find texexec.ini. But it's there, in > > \localtexmf\context\config (as well as \texmf\context\config) > > > BTW, if I execute kpsewhich texexec.ini it returns without an error, but > > also with no information. Is that right? > > Yes, and that's the problem. Recent ConTeXts are too strongly > tied to fpTeX :\ > > One thing you can do: move your texexec.ini in the same folder > as texexec.pl
Thanks, but that didn't work. I still have a nagging feeling that I'm forgetting something simple. MiKTeX comes with a texexec.exe. Putting texexec.ini in the same directory doesn't do it either. Is there an environment variable that I can set to help texexec find its way? Or a command line switch? (I have not found mention of either in the docs) (Putting texexec.ini in the directory containing the ConTeXt .tex script works.) -gary _______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
