From: cym224@gmail.com (Nemo)
Subject: [TUHS] MS-DOS
Date: Sat, 2 Jul 2016 15:46:21 -0400 [thread overview]
Message-ID: <CAJfiPzy9DpOPWuHmOu79-C7fG6F074q9SVBhxquARVJqoTscPQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1607021130440.78278@frieza.hoshinet.org>
On 2 July 2016 at 11:32, Steve Nickolas <usotsuki at buric.co> wrote:
[...]
> (Actually, I was trying to see if I could make a sort of quasi-'nix out of
> OS/2 1.0 using Watcom. ;) Haven't been doing too well at that because of
> Watcom's limited libc.)
The MKS Toolkit for OS/2 along with gcc+emx gave a second-order
approximation. (And Warp Connect had 'Net tools, even remote logins
with the former.)
N.
next prev parent reply other threads:[~2016-07-02 19:46 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 15:17 [TUHS] Algol68 vs. C at Bell Labs scj
2016-06-30 5:06 ` Dave Horsfall
2016-06-30 5:08 ` John Cowan
2016-06-30 11:18 ` arnold
2016-06-30 11:45 ` arnold
2016-06-30 13:22 ` Clem Cole
2016-06-30 14:05 ` Marc Rochkind
2016-06-30 14:33 ` William Cheswick
2016-06-30 14:43 ` Ronald Natalie
2016-06-30 14:57 ` Joerg Schilling
2016-06-30 15:07 ` Ori Idan
2016-06-30 23:07 ` Dave Horsfall
2016-07-01 3:27 ` Jesus Cea
2016-06-30 15:32 ` Dan Cross
2016-06-30 15:49 ` Larry McVoy
2016-06-30 16:32 ` Clem Cole
2016-07-04 5:08 ` [TUHS] OS for IBM PC (was: Algol68 vs. C at Bell Labs) Greg 'groggy' Lehey
2016-06-30 17:07 ` [TUHS] Algol68 vs. C at Bell Labs John Cowan
2016-06-30 17:57 ` Marc Rochkind
2016-06-30 18:31 ` Dan Cross
2016-06-30 19:21 ` Clem Cole
2016-06-30 19:51 ` Dan Cross
2016-06-30 19:55 ` Clem Cole
2016-06-30 20:04 ` Dan Cross
2016-06-30 18:26 ` Steve Nickolas
2016-06-30 19:21 ` Diomidis Spinellis
2016-06-30 19:43 ` Dan Cross
2016-06-30 19:53 ` Clem Cole
2016-06-30 19:47 ` Clem Cole
2016-06-30 20:57 ` Nemo
2016-06-30 23:11 ` Random832
2016-06-30 23:16 ` Marc Rochkind
2016-06-30 23:38 ` Random832
2016-07-01 0:38 ` Clem Cole
2016-07-01 1:21 ` Marc Rochkind
2016-07-01 1:34 ` John Cowan
2016-07-04 19:23 ` Dave Horsfall
2016-07-04 19:56 ` Ronald Natalie
2016-07-01 2:35 ` Nemo
2016-07-01 3:01 ` Kurt H Maier
2016-07-01 3:52 ` Lyndon Nerenberg
2016-07-01 12:47 ` [TUHS] MS-DOS William Cheswick
2016-07-01 13:43 ` Marc Rochkind
2016-07-01 21:58 ` John Cowan
2016-07-01 22:27 ` Jacob Ritorto
2016-07-01 22:54 ` Jacob Goense
2016-07-01 23:44 ` John Cowan
2016-07-02 0:08 ` Steve Nickolas
2016-07-02 1:09 ` Kurt H Maier
2016-07-02 2:59 ` Dave Horsfall
2016-07-02 3:27 ` Greg 'groggy' Lehey
2016-07-02 23:21 ` Dave Horsfall
2016-07-01 23:49 ` Dave Horsfall
2016-07-02 1:12 ` Steve Nickolas
2016-07-02 4:37 ` SZIGETI Szabolcs
2016-07-02 9:53 ` Brantley Coile
2016-07-01 13:47 ` Clem Cole
2016-07-01 15:13 ` Steve Nickolas
2016-07-02 15:25 ` Ronald Natalie
2016-07-02 15:32 ` Steve Nickolas
2016-07-02 19:46 ` Nemo [this message]
2016-07-03 1:18 ` Steve Nickolas
2016-07-03 13:33 ` Nemo
2016-07-01 17:39 ` John Cowan
2016-07-02 15:17 ` Ronald Natalie
2016-07-03 22:07 ` Derek Fawcus
2016-07-02 23:32 ` [TUHS] Algol68 vs. C at Bell Labs Peter Jeremy
2016-06-30 15:52 ` Joerg Schilling
2016-06-30 20:47 ` Lawrence Stewart
2016-07-02 0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02 1:13 ` Steve Nickolas
2016-07-02 4:52 ` Random832
2016-07-03 19:40 ` scj
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=CAJfiPzy9DpOPWuHmOu79-C7fG6F074q9SVBhxquARVJqoTscPQ@mail.gmail.com \
--to=cym224@gmail.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).