Re: lynx-dev ms client

[Klaus Peter Wegge]

> 
> Well, I was messing around with a copy of microsoft client for dos.  I can
> get on my win95 based network for filesharing using this dos only machine
> and ms client.  
> 
> I also have tcp/ip setup and i can successfully ping any machine on my lan.
> 
> However, I couldnt get lynx to work.  It says no packet driver found.  I
> have an ne2000 compatible.  I downloaded crynwr's ne2100 packet driver,
> successfully built it, and couldnt get it to init the nic.  This was either
> with the msclient started or not.
OK don't know very much about MS CLIENT.
But some ideas:
lynx uses an own TCP/IP-Stack, waterloo TCP, which is compiled in.
It needs the packet driver for your ethernet card loaded.
A simultanious use of of two or more packetdriver under DOS
needs a so called packet-multiplexer, which I didn't get to work.
That means, you either use lynx on top of the ne2000 packet driver
or MS CLIENT, which I think also needs that same NE2000packetdriver!
A firmeware NE2000 packetdriver should be available at differnet vendor
sites. If not, mail me personally.
When starting lynx, you should be sure, only the packet driver
is in memory and nothing else is using it.
If you aren't, simply uninstall the packet driver and it will
tell you more about possible usage. and reinstall it by hand.the 

> 
> What reason would there be for lynx not to recognize the tcp/ip stack that
> was installed by ms client and is already running.
> 
> Not knowing an darn thing about packet drivers, whats the diff between a
> packet driver and a tcp/ip stack installed by ms-client?

Klaus-Peter