From: Scott Blachowicz <scott@bloke.statsci.com>
Cc: "(ding)" <ding@ifi.uio.no>
Subject: Re: UUdecode and NTemacs
Date: Mon, 07 Apr 1997 11:30:28 -0700 [thread overview]
Message-ID: <m0wEJBV-000QdNC@bloke.statsci.com> (raw)
In-Reply-To: Your message of "07 Apr 1997 12:45:28 -0400." <wksp1293yv.fsf@peorth.gweep.net>
Stainless Steel Rat <ratinox@peorth.gweep.net> wrote:
> DJGPP builds DOS programs, not Win32 console programs. This is a problem
> because GNU Emacs on Win32 platforms can have exactly one DOS program
> running underneath it. Start bash.exe and try to invoke your DOS uudecode
> program and Emacs will lock up, and you will not be able to break out.
It also means that you can't see long filenames from NT, but that you can from
Win95. The Win95 "DOS" portion identifies itself as DOS 7.0 and handles the
DPMI INT mumble that gets LFN information. The NT "DOS" stuff IDs as DOS 5.5
(I think) and doesn't handle that DPMI interrupt. I've run into this problem
trying to migrate a GNUmake-based build environment from Win95 to NT (3.51 and
4.0). If anyone knows otherwise, I'd like to hear about it...
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
next prev parent reply other threads:[~1997-04-07 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-04 8:59 Fabrice POPINEAU
1997-04-04 19:32 ` Lars Magne Ingebrigtsen
1997-04-04 23:08 ` Dewey M. Sasser
1997-04-04 23:17 ` Stainless Steel Rat
1997-04-05 10:49 ` Lars Magne Ingebrigtsen
1997-04-07 7:51 ` Fabrice POPINEAU
1997-04-07 16:42 ` Stainless Steel Rat
1997-04-07 8:01 ` Andy Eskilsson
1997-04-07 16:45 ` Stainless Steel Rat
1997-04-07 18:30 ` Scott Blachowicz [this message]
1997-04-07 19:00 ` Stainless Steel Rat
1997-04-07 19:41 ` Scott Blachowicz
1997-04-07 19:58 ` Richard Hoskins
1997-04-08 18:05 ` Andrew Innes
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=m0wEJBV-000QdNC@bloke.statsci.com \
--to=scott@bloke.statsci.com \
--cc=ding@ifi.uio.no \
--cc=scott@statsci.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 NNTP newsgroup(s).