The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Floppy to modern files for Usenet maps
Date: Mon, 24 Jun 2019 21:07:48 +0000	[thread overview]
Message-ID: <20190624210748.lpkrouguj4sy7b7b@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <bb6f6575-0497-a78d-61af-dbb4321a944b@spamtrap.tnetconsulting.net>

On 23 Jun 2019 18:02 -0600, from tuhs@minnie.tuhs.org (Grant Taylor via TUHS):
> I wonder what the requirements are for INTERLNK & INTERSVR.  I don't know if
> they would go back to (MS-)DOS 2.11 or not.

The OS/2 Museum claims at [1] that the network redirector was added in
3.0. I'd expect INTERLNK/INTERSVR to need redirector support, and if
that assumption is correct, those wouldn't work on any pre-3.0
versions of Microsoft's DOS (whether MS-DOS or PC-DOS), and support
may be spotty on versions earlier than the one where they were
introduced depending on which exact features are used.

Also, a cursory glance at a MS-DOS 3.1 user's manual and user's
reference that I have lying around does not list INTERLNK/INTERSRV in
the command reference, so those would presumably have come later than
that. Wikipedia appears to confirm this at [2] by claiming they were
introduced in PC-DOS 5.02 / MS-DOS 6.0; the cited source at [3], [4]
simply says "6.0 and later" without specifying a variant.

So, almost certainly not that easy, unfortunately.


[1] http://www.os2museum.com/wp/dos/dos-3-0-3-2/

[2] https://en.wikipedia.org/wiki/List_of_DOS_commands#INTERSVR_and_INTERLNK

[3] http://www.easydos.com/interlink.html

[4] http://www.easydos.com/intersvr.html

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
  “The most dangerous thought that you can have as a creative person
              is to think you know what you’re doing.” (Bret Victor)

  parent reply	other threads:[~2019-06-24 21:08 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23 23:10 Mary Ann Horton Gmail
2019-06-23 23:52 ` Arthur Krewat
2019-06-24  0:02   ` Grant Taylor via TUHS
2019-06-24  0:35     ` Mary Ann Horton Gmail
2019-06-24  0:53       ` Arthur Krewat
2019-06-24  0:56         ` Larry McVoy
2019-06-24  1:12           ` Arthur Krewat
2019-06-24  1:31             ` William Pechter
2019-06-24  1:51               ` Arthur Krewat
2019-06-24  1:40         ` Bakul Shah
2019-06-24  3:20           ` Grant Taylor via TUHS
2019-06-24  0:50     ` Arthur Krewat
2019-06-24 21:07     ` Michael Kjörling [this message]
2019-06-24 21:30       ` Steve Nickolas
2019-06-24 21:59         ` Gregg Levine
2019-06-23 23:57 ` Grant Taylor via TUHS
2019-06-24  0:40   ` Mary Ann Horton Gmail
2019-06-24  1:37     ` William Pechter
2019-06-24  3:17     ` Jason Stevens
2019-06-24  1:57   ` Steve Nickolas
2019-06-24  2:09     ` pechter
2019-06-24  0:03 ` Theodore Ts'o
2019-06-24  0:19 ` Seth Morabito
2019-06-24  0:33 ` Larry McVoy
2019-06-24  1:58   ` Steve Nickolas
2019-06-25  3:54 ` Jonathan Gevaryahu
2019-06-25 11:21   ` ckeck
2019-07-09 16:28 ` Mary Ann Horton Gmail
2019-07-09 16:53   ` KatolaZ
2019-07-09 17:12   ` Henry Bent
2019-07-09 17:25     ` Seth Morabito
2019-07-09 17:34       ` Henry Bent
2019-07-09 19:19         ` Henry Bent
2019-07-09 19:41           ` Richard Salz
2019-07-09 20:09           ` Grant Taylor via TUHS
2019-07-09 20:58             ` Henry Bent
2019-07-09 20:54           ` Mary Ann Horton Gmail
2019-07-09 21:30             ` Grant Taylor via TUHS
2019-07-09 21:35               ` Grant Taylor via TUHS
2019-07-09 21:37             ` Grant Taylor via TUHS
2019-07-09 21:46               ` Henry Bent
2019-07-09 22:02                 ` Henry Bent
2019-07-09 23:23                   ` Mary Ann Horton Gmail
2019-07-10  0:06                     ` Dan Cross
2019-07-10  0:26                       ` Grant Taylor via TUHS
2019-07-10  0:38                         ` Dan Cross
2019-07-10  0:49                           ` Larry McVoy
2019-07-10  0:57                             ` Clem Cole
2019-07-10  1:26                               ` [TUHS] V0 B Compiler Warren Toomey
2019-07-10  1:29                                 ` Clem Cole
2019-07-10  1:32                                   ` [TUHS] Plot 10 Sources Clem Cole
2019-07-10  2:51                                     ` Charles Anthony
2019-07-10  3:00                                       ` Charles Anthony
2019-07-10  3:01                                       ` Clem Cole
2019-07-10 12:51                                     ` Nelson H. F. Beebe
2019-07-10 14:34                                       ` Clem cole
2019-07-10  1:02                             ` [TUHS] Floppy to modern files for Usenet maps Arthur Krewat
2019-07-10  1:19                               ` Larry McVoy
2019-07-10  1:34                                 ` Dave Horsfall
2019-07-10  0:28                       ` Mary Ann Horton Gmail
2019-07-09 22:01               ` Mary Ann Horton Gmail
2019-07-09 22:44                 ` Grant Taylor via TUHS
2019-07-09 23:14                   ` Mary Ann Horton Gmail
2019-07-10  0:24                     ` Grant Taylor via TUHS
2019-07-10  1:13                       ` Mary Ann Horton Gmail
2019-07-09 17:33     ` Clem Cole
2019-07-15  3:21   ` [TUHS] Historical " Mary Ann Horton Gmail

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=20190624210748.lpkrouguj4sy7b7b@h-174-65.A328.priv.bahnhof.se \
    --to=michael@kjorling.se \
    --cc=tuhs@minnie.tuhs.org \
    /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).