>> I have an old 386 at home that my kids use. They want to use the
>> Arachne web browser but it uses something called odipkt and lsl (I
>> think its the same lsl the Novell uses).
>
>>From what I can remember about packet drivers and LSL, neither one of
>them implements a TCP/IP stack. From what I recall, the LSL is merely a
>way to put Netware packets through the same packet driver as IP packets,
>and it may not even be needed in your particular case.
Actually, this isn't true. Novell came out with a package called
Lan WorkPlace that had a ODI-style TCP/IP stack built-in. It wan't
fast but it worked and Lan WorkPlace also came with command and GUI
versions of FTP, TELNET, etc. For the time, it was nice!
>I used a package called NCSA Telnet, which was a DOS program that
>implemented a full-fledged TCP/IP stack, inside the program itself. It
>only used the packet driver to send ethernet frames (which is what a
>packet driver does, anyway). But, the major things that need to be
>configured, such as IP address, gateway, DNS, etc., were all configured
>within the top-level DOS program (in my case NCSA Telnet).
Yup.. thats one way to do it. You can also find Winsock tools that
will interface to packet drivers. I beleive Trumpet can still do this.
--David
.----------------------------------------------------------------------------.
| David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
!---- ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
