Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!esseye!jdbbs!wybbs!douglas
From: douglas@wybbs.mi.org (Douglas Mason)
Newsgroups: comp.sys.novell
Subject: Re: Novell Certfication (hardware)
Message-ID: <606@wybbs.mi.org>
Date: 12 Jan 91 01:57:53 GMT
References: <1991Jan9.112347.37512@eagle.wesleyan.edu> <1991Jan10.183900.22664@world.std.com> <20591@netcom.UUCP> <YETSKO.91Jan11084848@int
Reply-To: douglas@wybbs.UUCP (Douglas Mason)
Organization: Consultants Connection, Jenison MI
Lines: 22

In article <YETSKO.91Jan11084848@interlan.interlan.com> yetsko@interlan.interlan.com writes:

>But with 'certified' hardware/software you put the panic on Novell to get
>a solution.  Novell in turn can put the panic on the involved parties, 
>or else they can pull certification.  (Yes, they DO pull it for later 
>discovered bugs until they are fixed!)
>


Ah...  "Panic Novell"?  Jesus, we had tried everything short of taking some
reps hostage in order to get the TCP/IP NLM.  Not too much panic shown there.

With some of our "Novell Certified" machines, we installed such "panic" in
the technical support people that it barely took a WEEK for them to call us
back.  By then the problem was so old that it took a discussion to figure
out what they were calling about.

Sure, I bad-mouth the support, but I DO love Netware 3.1.  Really!  :-)

-Doug

Douglas Mason | Network Administrator | ITM Corp. | Grand Rapids, Mich