🚀 go-pugleaf

In article <3qntku$fe2@maze.dpo.uab.edu>, <demb007@uabdpo.dpo.uab.edu> writes:
> Path: news0.cybernetics.net!newsjunkie.ans.net!howland.reston.ans.net!swrinde!emory!darwin.sura.net!maze.dpo.uab.edu!usenet
> From: demb007@uabdpo.dpo.uab.edu  (Bud Porter)
> Newsgroups: bit.listserv.novell,comp.sys.novell,comp.os.netware.misc
> Subject: First time install of Netware 4.1
> Date: 2 Jun 1995 20:51:42 GMT
> Organization: University of Alabama at Birmingham
> Lines: 10
> Message-ID: <3qntku$fe2@maze.dpo.uab.edu>
> Reply-To: demb007@uabdpo.dpo.uab.edu (Bud Porter)
> NNTP-Posting-Host: tty3.maze.ppp.uab.edu
> X-Newsreader: IBM NewsReader/2 v1.1a
> Xref: news0.cybernetics.net bit.listserv.novell:6588 comp.sys.novell:14872 
comp.os.netware.misc:2356
> 
> I have a friend who will be installing Netware 4.1 for the
> first time. He has a good deal of experience with 3.12.
> 
> Any words of wisdom, suggestions, etc. would be greatly
> appreciated.
> 
> ___________________________
> Bud Porter
> demb007@uabdpo.dpo.uab.edu
> 
> 
Be careful, and read thoroughly before hand.  Getting the "knack" of designing 
the NDS to limit future changes takes a little while.  Novell, and one 
particular ISV (makes a product called DS Standard) have made it easier to 
change the NDS in the future, but it still requires some thought.  Such as:  
how many subordinate relationships are you creating in the NDS, and many other 
issues.

Other than the NDS issues, make sure you have the latest patches, disk 
drivers, LAN drivers, etc.  I have noticed that 90% of the problems I have 
seen with NetWare 4.1, 4.1 SFTIII, and 4.1 SMP are due to incompatibilities 
with the drivers.  Research this toroughly.

This is very brief, if you (or your friend) would like more info email me, and 
we will discuss it.  Depending on your project, I have some interesting 
material that might be of interest to you.

Jeff Seals
CNE/ECNE
wic@cybernetics.net