Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!jade!violet.berkeley.edu!gts
From: gts@violet.berkeley.edu (Greg Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: standard interface
Message-ID: <6026@jade.BERKELEY.EDU>
Date: Sat, 21-Nov-87 23:34:06 EST
Article-I.D.: jade.6026
Posted: Sat Nov 21 23:34:06 1987
Date-Received: Tue, 24-Nov-87 06:27:39 EST
Sender: usenet@jade.BERKELEY.EDU
Reply-To: gts@violet.berkeley.edu (Greg Small)
Organization: University of California, Berkeley
Lines: 24

= From: karn@faline.bellcore.com (Phil R. Karn)
= Date: 21 Nov 87 02:39:19 GMT
= Organization: Bell Communications Research, Inc
= 
= I see little hope of establishing a standard application/transport
= interface on the PC until we can trash MS-DOS in favor of a "grownup"
= operating system. I'm not willing to sacrifice concurrent applications.

Actually, multiple network applications can easily run on Netbios or TCP-IP
because they can be called by a resident network driver when activity occurs.
I have not been following this discussion closely but I surmise that this is
what "up call" means (Netbios calles them "post interrupts").

Actually "grown up" operating systems are too bulky and inefficient for the
many, many applications that are ideal for a PC class workstation.  Just
because DOS/BIOS is a small, highly accessable operating system doesn't mean
that is cannot participate in concurrent network applications.

Gregory T Small                                      (415)642-5979
Personal Computer Networking & Communications        gts@jade.Berkeley.EDU
Data Communications and Networking Group             ucbvax!jade!gts
Computer Facilities and Communications               SPGGTS@UCBCMSA.BITNET
216 Evans Hall CFC
University of California, Berkeley, Ca 94720