home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!VM1.ULG.AC.BE!PIRARD
- From: PIRARD@VM1.ULG.AC.BE (Andre' PIRARD)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: NDIS packet driver in DOS window?
- Message-ID: <9208211016.aa04579@louie.udel.edu>
- Date: 21 Aug 92 13:52:25 GMT
- References: <backman@FTP.COM>
- Sender: usenet@ucbvax.BERKELEY.EDU
- Organization: University of Liege (Belgium), SEGI (Computing Center)
- Lines: 26
-
- [The original question is about using PDs, so forgive the Subject sliding]
- On Sat, 20 Jun 1992 13:07:09 -0400 Larry Backman said:
- >I'll make the same statement I made on comp.os.os2.xxx.
- >
- >The correct solution to this problem is to write an OS/2 Virtual Device
- >Driver that takes packet driver requests from one or more DOS boxes and
- >converts those requests into calls to an NDIS driver.
- >...
-
- This wouldn't allow several DOS apps to share the same IP address,
- nor OS/2 TCP/IP's [ban PKTMUX], though.
- Another approach is to encapsulate IP in a protocol already shared
- by DOS, and NETBIOS is (with ES presently, but soon without, I am told).
- So, one uses NB.COM with a different IP address in each DOS.
- (I haven't tried NB under OS/2 yet, but I am using it under DESQview OK).
- And, of course, a NB/IP gateway on the LAN.
- PCROUTE does this nicely (I am using it with 2 PDs: IBMTOKEN and NB,
- both on IBM's LANSUP).
-
- Of course, the best idea would be to provide OS/2 TCP/IP's API in DOS.
- It looks like IBM wants to do that.
- So, isn't this the occasion to define the specs of the DosSocketAPI?
-
- Andr'e PIRARD SEGI, Univ. de Li`ege 139.165 IP Adm.
- B26 - Sart Tilman B-4000 Li`ege 1 (Belgium) +32 (41) 564932
- pirard@vm1.ulg.ac.be alias PIRARD@BLIULG11.BITNET
-