From: eMaXer <zxy@yxz67483.com>
Subject: Re: Problem with Emacs Info and gzipped files on Cygwin
Date: Sun, 25 Jan 2004 21:40:48 GMT [thread overview]
Message-ID: <uu12jk8pb.fsf@yxz67483.com> (raw)
In-Reply-To: mailman.1297.1075010266.928.help-gnu-emacs@gnu.org
>>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
>> Newsgroups: gnu.emacs.help From: eMaXer <zxy@yxz67483.com> Date:
>> Sat, 24 Jan 2004 20:16:08 GMT
>>
>> Hi, I am using NTEmacs (GNU Emacs 21.3.1) on Windows XP, and
>> Cygwin 1.5.5-1. When I try to use Emacs Info, if the info file is
>> gzipped an error message window pops up with the following
>> message :
>>
>> "The NTVDM CPU has encountered an illegal instruction. CS:0726
>> IP:ffd8 OP:fe ff 00 00 00 Choose 'Close' to terminate the
>> application."
>>
>> The message window has the title "16 bit MS DOS Subsystem".
>>
>> The error happens in the function call-process-region. The
>> following code produces the same error:
>>
>> (call-process-region (point-min) end-of-gzipped "gunzip" t t nil)
Eli> What port of gzip/gunzip do you have? If it's a DOS port, I'd
Eli> try to replace it with a native Windows port. (I suspect that
Eli> it's a DOS port because NTVDM, the NT Virtual DOS Machine,
Eli> a.k.a. NT DOS emulator, does not kick in unless you run a DOS
Eli> program.)
Thanks for the hint. The port is the one that comes with the Cygwin
distribution, I do not know if it is DOS or anything else.
Removing the symbolic link from gunzip to gzip (as suggested by Thomas
Haselberger) solved the problem.
--
In the beginning was the Word,
and the Word was in a buffer,
and the buffer was in Emacs.
next prev parent reply other threads:[~2004-01-25 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 20:16 Problem with Emacs Info and gzipped files on Cygwin eMaXer
2004-01-25 5:58 ` Eli Zaretskii
2004-01-25 14:27 ` Thomas Haselberger
2004-01-25 21:36 ` eMaXer
[not found] ` <mailman.1297.1075010266.928.help-gnu-emacs@gnu.org>
2004-01-25 21:40 ` eMaXer [this message]
2004-01-26 5:58 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uu12jk8pb.fsf@yxz67483.com \
--to=zxy@yxz67483.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).