delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2001/05/31/13:15:19

Sender: root AT gull DOT mail DOT pas DOT earthlink DOT net
Message-ID: <3B16640D.A83A6F02@earthlink.net>
Date: Thu, 31 May 2001 09:32:29 -0600
From: Thomas A Webb <tawebb AT earthlink DOT net>
Organization: Wordwonder.com - an E-zine
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: OpenDosList <opendos AT delorie DOT com>
Subject: DRDOS and IP
References: <200105311448 DOT HAA25867 AT snipe DOT mail DOT pas DOT earthlink DOT net>
Reply-To: opendos AT delorie DOT com

 "da Silva, Joe" wrote:
  ---------
 > However, what I was asking about the Trumpet TCP/IP stack was ...
 > is that the Trumpet stack for Windoze or the one for DOS? Also, I
 > am interested to know if your "IE5 over W3.1 install" used M$-DOS
 > or DR-DOS as the underlying O/S?  <g>
 >
 
I'm using the Win31 version of trumpet, and dr-dos as the platform.
 
 > BTW, I cannot agree with your posting about Lan Manager vs. Novell,
 > as I find the Lan Manager (MS Client) stuff uses far more
conventional
 > memory (particularly as the Novell Client32 stuff could run in
extended
 > memory, leaving lots of free upper memory too :-).
 
I completely agree that Novell is better cleaner stuff than Microsoft's
lan manager. I was reacting to the idea running *both*. I was an IT
manager for years in an environment with hundreds of PCs in facilities
spread all over the country, and I standardized on Novell because of
it's stability and clean use of resources. 

Novell architecture was not designed with the Internet in mind, and when 
you want transparent access to the Internet and IP services, a cobbled
up 
combo makes no sense to me in that it involves layers in the protocol
stack 
that add opportunities for neurotic behavior (both computer and operator
:-) )  
My choices lean to simplicity, since I'm the one that has to fix it when
it breaks :-)
 
INMO, if we step back a pace and look at what we are doing, it's often
better to use a simple solution that gets the functionality we want
rather than adding bricks to an existing edifice. I have personally used
SOS, XFS, Lanmanager, and Novell as shared-workspace networking
solutions for DRDOS/MSDOS, and most or all of the functionality I was
looking for is available in any one of them. 

Whatever floats your boat, in the final analysis..
 
 --
Thomas  Webb
Come visit at http://wordwonder.com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019