From: "Marcela I. Avalos" <marcelaavalof@dingoblue.net.au>
Subject: Re: Re[2]: Problem installing context with miktex
Date: Sun, 8 Jul 2001 10:53:27 +1000 [thread overview]
Message-ID: <005f01c10748$782c6660$78be8ec6@massey.ac.nz> (raw)
In-Reply-To: <5.1.0.14.0.20010707194054.00a97ea0@public.uni-hamburg.de>
Yes, I set the paths, renamed the scripts to use .exe for the scripts.
However, when I run texexec everytime I get an error saying that the
commands are not recognized. The only command that works is --verbose. I
will certainly upgrade to Miktex 2.1 (this afternoon, Australian time) and
see if context works in that case. MOst probably I will ask a few questions
later.
Cheers,
Luis
----- Original Message -----
From: Eckhart Guthöhrlein <eckhart_guthoehrlein@public.uni-hamburg.de>
To: Hans Hagen <pragma@wxs.nl>; Luis A. Apiolaza <luis.apiolaza@utas.edu.au>
Cc: Context Support List <ntg-context@ntg.nl>
Sent: Sunday, July 08, 2001 3:59 AM
Subject: Re: Re[2]: Problem installing context with miktex
> At 16:17 07.07.2001 +0200, Hans Hagen wrote:
> > >Just in case I am running ActiveState Perl 5.6.1.628, Miktex 2.0 in
> > >Windows NT 4.00.1381 SP6, 512 Mb RAM and plenty of HD space. Any help
> > >will be appreciated.
> >
> >well, there are miktex users on this list; is there anyone who uses
miktex
> >on win nt?
> >
> >is pdftex / pdfetex recognized as a valid program?
>
> Well, I followed the discussion, but I don't know what the problem is. I'm
> using MikTeX 2.1 with Windows 2000 SP1, ActivePerl 5.6.0.623, and
> everything works fine. I followed the instructions as Luis seems to have
> done it, set up the paths etc. Just to make sure: do you have a complete
> MikTeX installation *including pdfetex*? Did you add /texmf/context/perltk
> to your path, with runperl.exe renamed in this directory? (Don't want to
> insult your intelligence...)
> I tried without pdfetex on my machine, but my error message differs ('The
> command "pdfetex" has been written incorrectly or cannot be found.') The
> lines Luis has in his .tmp file, are they written by texexec? I assume
> this, so a problem calling pdfetex might be the reason. If not, I don't
> have any more ideas for now.
> Btw, I can recommend upgrading to miktex 2.1, the automatic package
> updating is a nice feature (well, at least for LaTeX users with dozens of
> add-on packages, but the context archive is not yet up-to-date, i think,
so
> knowing the manual way is always an advantage).
>
> Eckhart
>
>
next prev parent reply other threads:[~2001-07-08 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 9:46 Luis A. Apiolaza
2001-07-07 14:17 ` Hans Hagen
2001-07-07 17:54 ` Re[4]: " Giuseppe Bilotta
2001-07-07 17:58 ` Re[2]: " Richard Hensh
2001-07-07 17:59 ` Eckhart Guthöhrlein
2001-07-08 0:53 ` Marcela I. Avalos [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 17:08 Hans Hagen
2001-07-07 8:26 ` Re[2]: " Luis A. Apiolaza
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='005f01c10748$782c6660$78be8ec6@massey.ac.nz' \
--to=marcelaavalof@dingoblue.net.au \
--cc=writetomarce@yahoo.com.au \
/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).