public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin-talk@cygwin.com" <cygwin-talk@cygwin.com>
Cc: 'carolus' <worwor@bellsouth.net>
Subject: RE: How to read thumb drive volume label
Date: Wed, 16 Mar 2011 01:46:00 -0000	[thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A209DAA100A6@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <ilmo2h$bg9$1@dough.gmane.org>

carolus sent the following at Monday, March 14, 2011 11:57 PM
>On 3/14/2011 4:55 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> (Personally, I think that running DESQview386 under DOS 3.3 was better
>> than any version of Windows, just as some people on this list wax
>> nostalgic for B20 and version 1.5.)  :-)
>
>I never thought much of DESQview or of Windows either. At that time I
>used to telnet from DOS 3.3 to a Unix box, and was happier in Unix. It
>took less than a day to switch to Cygwin, with hardly any difference
>from the real Unix. Before that I was using the MKS Toolkit on my DOS
>or Windows desktop, which was nice software, but not as complete an
>emulation as Cygwin.

You may have misunderstand.  I *liked* DESQview.

At the time, I also liked the MKS Toolkit.  Of course, that was years
before cygwin existed.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

       reply	other threads:[~2011-03-16  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D7E200C.40707@bellsouth.net>
     [not found] ` <0105D5C1E0353146B1B222348B0411A209DAA1008C@NIHMLBX02.nih.gov>
     [not found]   ` <illhr5$l71$1@dough.gmane.org>
     [not found]     ` <0105D5C1E0353146B1B222348B0411A209DAA10090@NIHMLBX02.nih.gov>
     [not found]       ` <ilmo2h$bg9$1@dough.gmane.org>
2011-03-16  1:46         ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-03-16  4:08           ` Christopher Faylor
2011-03-16  4:24             ` Christopher Faylor

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=0105D5C1E0353146B1B222348B0411A209DAA100A6@NIHMLBX02.nih.gov \
    --to=bbuchbinder@niaid.nih.gov \
    --cc=cygwin-talk@cygwin.com \
    --cc=worwor@bellsouth.net \
    /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).