Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!nuug!ulrik!fiol!edmbv
From: edmbv@fiol.UiB.NO (Bjorn Asle Valde)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Q: can LM/x and pc/tcp share tcp/ip stack?
Summary: A cunning plan...
Keywords: ndis, lan-manager, pc-tcp, tcp/ip
Message-ID: <1991Feb6.081311.4256@ulrik.uio.no>
Date: 6 Feb 91 08:13:11 GMT
References: <1991Feb4.120459.15972@ulrik.uio.no> <1991Feb5.111900.14265@hemel.bull.co.uk>
Sender: news@ulrik.uio.no (USENET News System)
Organization: University of Bergen, Norway.
Lines: 26

In article <1991Feb5.111900.14265@hemel.bull.co.uk> pmoore@hemel.bull.co.uk (Paul Moore) writes:

>I had been thinking along similar lines but in a different way.
>Lan Manager is a NetbIos application. PC/TCP supply a NetbIos for their
>kernel. It would seem simplest to throw away the HP NetBios over TCP
>and use only FTPs stack. If you dont do this you will end up with 2 tcp
>ip stacks in your PC - mucho memory cost.
>(This is the idea of the much vaunted "Open Systems" - treat it like a Lego
>set)

This reminds me of something my personal hero, Edmund Blackadder, once
spoke (yeah, bravo!) "I have a plan so cunning you could put a tail
on it and call it a weasel".  I doubt this will work, but will of course
investigate further. In '88 I visited MIT's media-lab and learned that
I only thought I knew what Lego is all about :-)

[The reason I'm sceptical is that I know HP has glued their l-m client
very thight to the transport stack. You can't for instance use, say,
Ungerman-Bass' tcp/ip stack]

Thanks net, Bjorn Asle
--
Bjorn Asle Valde - Humble Programer
edmbv@fiol.uib.no X.400: S=Valde;OU=cc;O=uib;P=uninett;c=no
Present address: TBK Bergen a/s, Pb 62, N-5031 Laksevaag Norway.
Phone +47-5-948200 fax. 948375