I see dozens of posts here concerning the 3.2 Novell client and the IPX NLM. The word *months* ago was that Revtech would be testing and determining what can be done.

* WELL? *

You cannot download versions of the client prior to 3.2 from Novells web page. This has become more than just an inconvenience, as it is costing many of us time and money.

"What we have here, is a failure to communicate". Lets see if someone at Revtech can address the issue before a user-riot ensues.

A knowledgebase Article will be posted stating the following:

Revelation Software has experienced Advanced Revelation connectivity problems resulting in server communication errors with Novell Netware Server 4.11 Support Pack 6 and Server 4.2 Support Pack 8a when running the Novell Intranetware Client32 for Windows 95/98 version 3.2.

If using the Novell Intranetware Client32 for Win95/98 v.3.2, Advanced Revelation sites using the Revelation NLM 1.5 will experience FS466 errors with the ?unable to boot media map? message.

OPENINSIGHT NOTE:

It should be noted that Novell Netware server 4.11 Support Pack 6 and server 4.2 Support Pack 8a and the Novell Intranetware Client32 v.3.2 were tested successfully when using the Revelation NLM 1.5 with OpenInsight 3.7.x.

SOLUTION (MARCH 2000):

Utilize the Novell Intranetware Client v.3.1 for an Advanced Revelation/Revelation NLM1.5 environment. You may obtain this client from Novell?s website at http://support.novell.com or dowload here. You may obtain this client version as part of the Novell subscription service, or download v 3.1 when it is made available from within this knowledgebase article.

This article should be posted by weeks end.

I had to install Arev on a new site.

You can't buy Novell 5.0 anymore, so I had to use Novell 5.1

It came with Client32 Ver 3.2

I had to waste hours downloading the last of the Novell client32 Ver 3.1 only to find nothing worked.

Your knowledgebase articles and workarounds are useless and have only resulted in many hours of wasted time trying to get and NLM that I paid many £££s for to work.

You ask big bucks for a product - then you should provide one that works.

If you keep your head buried in Java and fail to properly support your current user base, when you do get to lift your head you may find yourself deserted!!

YOUR WORKAROUNDS DON'T WORK AND I AM SICK OF WAITING FOR AN NLM THAT WORKS WITH TODAYS NETWORKING PRODUCTS!!

IT'S JUST NOT GOOD ENOUGH!!

Claude Mansutti

Ranting and raving gets you nowhere with RTI. Believe me, I've tried it in the past.

I realise, Warren that I'm not the first to rant and rave,

But the more people that complain, the more we poor unfortunates realise that we are not alone. Maybe one day RTI will realise that they aren't delivering what the community needs… hopefully before the community leaves them.

Also, it feels good to let off steam

Claude

I understand that much ofb the problems are to do with Novell & Microsoft. Indeed RevSoft have been trying to get Novell to pull its digit out for some time.

How about aking RevSoft for the incident number and then vent your emotion on Novell.

I agree, we need action but would seem the log jam is not (I hope) at RevSoft.

I was able to get the upgraded (fixed) CLIB.NLM from Novell and it resolves our problem with arev and oi not working with Novell 5.01

but you must use the 3.1 client with no service pack. And you must also map through dos to get Arev to work we run a special batch file that deletes the novell scripted drive mapping and then maps through dos. If you need the CLIB.NLM upgrade let me know.

Jhetu@tlcreates.com

Is the date on the CBIL.NLM 5/03/2000? We have rcv'd this version from Novell, but would like some sort of confirmation that it will work, before we put the "field test" version on our servers. I spoke to Revelation and the one they were able to confirm was data 4/19/2000, and had indicated that the problem had reappeared in later versions.

Matt Bavis

View this thread on the forum...