[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX] Re: none

From: David Kastrup
Subject: [AUCTeX] Re: none
Date: Mon, 20 Jun 2005 13:55:02 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Copying this reply to the AUCTeX list where it is ontopic.

"A. Jan Kutylowski" <address@hidden> writes:

> I am keen on installing latest auctex with preview latex for newest
> windows compilation of ntemacs and latest fptex. When I click on
> msys-1.0.8 I get the message:
> Die NTVDM-CPU hat einen ung├╝ltigen Befehl entdeckt. CS:0f8a IP:0119
> OP:656374 20 61. Should I ignore it?
> About the same with 1.0.10.
> Do I need to use MSYS to install auctex  (previously I had everything
> in site-lisp)?
> REgards,
> Dr. A. Jan Kutylowski
> Wissenschaftlicher Projektleiter
> (Senior Research Scientist)
> tel. +49-(0)351-46336171 (direct)
> fax. +49-(0)351-46336079
> *****
> Hannah Arendt Institute,
> Dresden University,
> 01062 Dresden, Germany,
> tel. +49-(0)351-46332802 (secretariat)

When in doubt, you could read the instructions.  You can also use
Cygwin, though we recommend using MSYS because it is typically faster,
and less complex.

This looks like you should rather file a problem report with MSYS than
with AUCTeX: this is the first I hear of such an effect.

On <URL:>

I read:

    What MinGW Is

    MinGW's official website is It is the best Windows port
    of GCC, the GNU Compiler Collection.

    The problem with DJGPP, another port of GCC that runs on Windows,
    is that it produces DOS executables that run in Windows XP's
    NTVDM, which is highly undesirable. Cygwin, yet another Windows
    port of GCC, produces executables that rely on an external DLL
    (bleah) and must be distributed under the GNU GPL unless you
    purchase a commercial license (bleah).

    MinGW suffers from none of these problems. It produces standalone
    Windows executables which may be distributed in any manner.

So NTVDM should not come into play at all.  It sounds like you are
either not actually using MSYS executables, or that you are calling
them from within a DOS box instead of an NT environment.

IIRC, clicking on the MSYS icon should open a shell window for you.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]