![](https://secure.gravatar.com/avatar/d8fd95a14acec745cbe25333b9505be9.jpg?s=120&d=mm&r=g)
Mats Broberg wrote:
I have also done the following since the first e-mail:
- Copied the contents of "texexec.rme" to "texexec.ini"
OK
- Uncommented the "set TeXShell to miktex" line in the new "texexec.ini" file.
- Added the string "C:\texmf\miktex\context\perltk" to the PATH (however, there is no "context" or "perltk" folder in the "miktex" folder. Shouldn't there be?)
As far as I remember, apart from installing Perl (ActivePerl) and adding it to PATH, I only had to add MikTeX's bin directory to PATH. Have you also generated the formats? From texexec.rme: ,---- | % If this file is called 'texexec.rme', copy it to 'texexec.ini', | % check the settings above, change them according to your TeX | % distribution, and say: | % | % texexec --verbose | % | % When set up properly, you should see your local settings fly by. | % When these settings are ok, the next call should work: | % | % texexec --make | % ^^^^^^^^^^^^^^^ | % and you should be able to process a file by saying | % | % texexec filename `---- And then of course, be sure to run: ,---- | mktexlsr `---- Regarding the files not having line breaks, I made the same mistake when I started using ConTeXt. The files have Unix end of line characters, so Notepad and other Windows-only editors will just give you a long string of garbage, as you discovered. Hans has put a lot of work in making Scite work nicely with ConTeXt, so you might find that helpful. Other users have their favorites (Emacs, jEdit, etc.). Good luck, Matthew