From: N8TM@aol.com
To: zyrain@brawleyonline.com, owner-gnu-win32@cygnus.com,
gnu-win32@cygnus.com
Subject: Re: BUG: False input = CRASH!
Date: Sun, 19 Jul 1998 06:11:00 -0000 [thread overview]
Message-ID: <81d50e9.35b1f057@aol.com> (raw)
In a message dated 7/18/98 1:50:51 PM, zyrain@brawleyonline.com wrote:
<<if you input a wrong command (ie, put
anything other than a command) Cygnus32 will hang the Windows95/NT
environment system. >>
But, under NT, you can enter ^C until the prompt comes back. Under W95, you
may end up rebooting.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-07-19 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-19 6:11 N8TM [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-07-20 1:44 Robert.Cross
1998-07-17 18:54 zyrain
1998-07-18 15:13 ` Michael Hirmke
1998-07-19 12:58 ` Rick Rankin
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=81d50e9.35b1f057@aol.com \
--to=n8tm@aol.com \
--cc=gnu-win32@cygnus.com \
--cc=owner-gnu-win32@cygnus.com \
--cc=zyrain@brawleyonline.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).