[comp.dcom.lans] Question about future prospects of BYU Novell packet driver

djc@duke.cs.duke.edu (David J. Cherveny) (10/12/90)

Lately I've been recommending the BYU/Packet Driver/Clarkson's CUTCP Telnet
solution for Novell users wishing to access other systems around Duke Medical
Center and the Campus.

So far his has worked great and I thank all who made it available.

Now I wonder about the future.  I know that all of these are officially
"unsupported" but are pretty well maintained by their keepers and they
generally make updates and fixes available.

My worry is with the BYU/Novell packet driver interface.  Not to pick on
BYU... since a similar argument could be applied to any of these programs...
but this is the one I worry about since a vendor ( Novell ) is involved.

Any ideas what may happen in the future?  When Novell releases new versions
of Netware, will the BYU interface break?  Will it be fixable?  Will someone
fix it?  Does BYU have an inside channel to Novell?  Is this sort of thing
supported/ignored/untollerated by Novell?  Can I sleep nights?  Am I neurotic?

Yea I know this a really vague question and I have lots of faith in the USENET
comunity as a whole.  I really like this solution and haven't seen one I
like better.

Thank you for any comments reguarding my concerns.


David Cherveny					djc@hodgkin.mc.duke.edu
Duke University Medical Center			(919)684-6804